messages during build:
device/samsung/s3ve3g-common/configs/nfcee_access.xml:9: namespace error : Namespace prefix android for signature on signer is not defined
Change-Id: I7f3a1588b9cf05cb6aff11ccc59d14e75cc6e98e
* 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
* Google killed it in Pie
* reference: LineageOS/android_frameworks_av@d0a98fa05
Change-Id: I9bfd354c3e3a3d4c193c3865ac7eae84719c02dc
Signed-off-by: Joshua Primero <jprimero155@gmail.com>
* 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
* msm8226-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
this gets enabled once you build eng flavours.
On userdebug builds this leads to init starting the console service which crashes and drains battery due to high cpu usage.
* Rename klte-common -> s3ve3g-common
* Drop fingerprint related blobs
* Drop camera shim, we do not need it
* Drop CameraWrapper to msm8226-common, as all msm8226 devices uses it
* Drop broadcom NFC
* Add buildable libpn547_fw.c, libpn547_fw_pku.c, libpn547_fw_platform.c dumped from stock S III Neo sources
* Update audio configs with stock S III Neo ones
* Update power_ext for S III Neo
* Drop broadcom WIFI for Qualcomm WIFI as we got a Qualcomm WIFI chip
* Drop broadcom bluetooth as we goot a Qualcomm bluetooth chip
* Update partitions for S III Neo
* Update rootdir for S III Neo
* Update overlay for S III Neo
* Update liblights path for S III Neo
* Update deviceperms for S III Neo
* Drop consumerir as we do not got an IR blaster
* Update TWRP files for S III Neo
* 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
* 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.
[haggertk: 15.1 backport - I noticed this now happening here too]
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
* 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
Unpublished
Adithya R
Rashed Abdel-Tawab
Bruno Martins
Joshua Primero
Kevin F. Haggerty
Francescodario Cuzzocrea
jrior001
Andre Eisenbach
nx111
Lucas Dupin
pythonlimited
Cal Archer
T H
Danny Baumann
Paul Keith
Nolen Johnson
Michael Bestas