Since we changed
DEVICE_MANIFEST_FILE := $(DEVICE_PATH)/manifest.xml
to
DEVICE_MANIFEST_FILE += $(DEVICE_PATH)/manifest.xml
the latter appends the mondrianwifi manifest.xml to the existing msm8974
manifest. So get rid of all the duplicate entries.
Change syntax to += to append mondrianwifi specific manifest.xml onto
existing msm8974 manifest.xml.
With the old :=, it overwrote the msm8974 manifest.xml.
Lineage has switched to clang for kernel builds by default. The
mondrianwifi 4.9 kernel does not build with clang.
Change-Id: Ie00632002a532a7a090d50c1951575c361244f7d
Use the default software implementation of gatekeeper.
Change-Id: Id696752ad78047155cad6a5dafe7ca1b4fe86345
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
This block is completely redundant because..
- WITH_DEXPREOPT := true is the default
- WITH_DEXPREOPT_PIC is never read
- DEX_PREOPT_DEFAULT := nostripping has no effect when the
BOARD_USES_SYSTEM_OTHER_ODEX flag is set to true
Test: make
Change-Id: I618a1e395ca1a14555cd50eef1a4f1aa079b553d
* There is zero reason to ever build without blobs. We've even seen
this situation with official builds from our servers. It's always
better for a build to fail than it is for it to produce something
that has no chance at working.
Change-Id: I4968795670c91f691e9ecdc0e4af62e16ba3a93a
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
We have issues with camera blobs which doesn't play
well with scudo allocation/deallocation tracking.
Scudo reports corrupted header when stopping a
video recording.
Because we aren't alone with this (also upstream seems
to have trouble with camera modules) use the 32 libc
which is used only by a few components, like camera
and audio.
Because docs states, that libc with the svelte take less RSS,
but is a little bit slower.
https://android.googlesource.com/platform/bionic/+/master/docs/native_allocator.md
This is the reason to not enable this target wide.
Change-Id: Ic0d950817238a227218f59b95e5fd2ffd66e786a
Also remove the widevine plugin we don't have
Reference:
LineageOS/android_hardware_interfaces@lineage-17.0/drm/1.1/README.md
Change-Id: Ie4ea8d79496ba6181ef6c45b0ce0a993a3e442c4
* So, this one from bullhead can cause everything to get janky AF
every time RenderScript is actually used, and finding one that
actually loads (no missing symbols) AND actually works well is,
well, challenging. The device works fine with the normal
non-adreno driver in AOSP, so let's use that until/unless we find
an actually working adreno driver.
Change-Id: I4ab19269eb49f5f2aed375d9055d68c1b9835f69
…nifest
* The cmd_list node exists, and it contains hover_mode, so
isSupported() returns true. Not having a supported interface
declared leads to boot-breaks starting with R.
Change-Id: If2081dc796ff1a33043d9894aa556028d4aa2d68
What this do is only write to core_ctl nodes every time the
screen turns on and off, as the new Lineage power HAL decides
to just change the migration value rather than messing with
cores, we may drop this as well.
Change-Id: I318268842aa0a4680883990bb8076e224ca9234d
