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
* Mounting /system partition is handled in kernel now,
however removing the entry from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
Note video HDR setting in Snap is only available
in Snap advanced settings at the very bottom of the menu.
Change-Id: Ia2d907aa5b20be6134bc3594684a423cf199f925
* We're messing with ownership and permissions here, so let's go
ahead and fix the context of this near worthless thing.
* The kernel will create it, we also write it here which will create
if it doesn't exist, so this is more manageable than chasing the
type_transition path
* The file is already labeled as a wifi_data_file, so fix this to
eliminate the below denial
avc: denied { read } for name=".wifiver.info" dev="mmcblk0p26"
ino=12 scontext=u:r:hal_wifi_default:s0
tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
Change-Id: Ie736b68f7d4d8559237b5cce072c6bf26f7ac4e7
