* 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
* 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
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
This makes bionic and various art tools that compile/runs cpu-specific
code choose the kryo variant at runtime. It does not affect
build-time compilation.
Bug: 120773446
Test: bionic benchmarks with and without this change
Change-Id: I670c8acd094090135515688c5f057c2cc08a083f
Follow blueline which has not demonstrated any regressions
after switching to a generic arch variant.
Bug: 120773446
Test: make
Change-Id: I9e23963fcfa5ccaa912f2930a632458c4d2a692d
* In the previous commit, I failed to note that TWRP
also needs the AIO property set, so append local path
to TARGET_RECOVERY_DEVICE_DIRS to make both Lineage
Recovery and TWRP happy.
Change-Id: Ie1d8dfa252dad02787544a73e9d4ee1d44d30dbf
* TARGET_USES_OVERLAY and USE_OPENGL_RENDERER are largely deprecated
* Don't set triple buffering, it introduces latency
* Don't use custom VSYNC offsets
Change-Id: If2892c83726c3558a96b28a8404f49982ebb9ba0
[haggertk: Only triple offset aspect of this change is relevant to
this device family]
* Due to "specialness" in our RIL library, ConnectivityService
doesn't seem to appropriately add the relevant directly-
connected routes, meaning that IPv4 mobile data is inoperable
due to lack of a default route. Let's reenable the legacy netd
behavior to get our connectivity back.
Change-Id: I59f8476ab36db0fb79856f74346e62e0dd4abae0
* Our platform requires 0x02000000U (USAGE_PRIVATE_UNCACHED) for
camera, video, and various other functionality
Change-Id: Ie5a8a46fef1c0f28ebd2cd3b3d29cc19763bc2a3
* These features have long been enabled by default in the audio HAL,
but things changed since the unification of the audio policy HAL.
Set all of them here, also to make it easily clear what is used.
Change-Id: I5bdb5fda3b9d5add5b9bac1f6980607761fbd692
* This is required to enable our legacy HAL1 camera recording
following OMX hardening in Ief2d2d4d0445074c0ecdc723b1b25997a7631389
Change-Id: Ide8dad10bf72fbd1acefec2f8ef4a90b0e3c0a4b
This reverts commit 24d70a1aec.
* The new HIDL power HAL seems to be appropriately riced^Wfixed for
8974 now.
Change-Id: I629ab2314dec4698a0d4d45d77cdc48bf92a4d74
Add a device-specific SunlightEnhancement CMHW class.
In addition to enabling outdoor mode, crank the display brightness
up, allowing for much better visibility in bright sunlight.
Change-Id: I6a87d438a0aecd9e068de932d4133e69e0563cf8
The recent change we made in the build repo makes all
builds dexpreopt only boot img and system server.
This changes angler builds back to full dexpreopt.
Change-Id: I0cf03634ee7bbc93b18b49d3f1efe82a6302b447
This reverts commit e955914336.
* As it turns out, the brand new HIDL power HAL isn't ready, at
least not for legacy devices like msm8974. Symptoms were that
after waking from sleep, cores 1-3 are not brought back online
consistently.
* Let's go back to the old thing, at least for now.
Change-Id: Ica2ddbeb42635662167efe0b48f0fe4051591b26
* The bulk of the device family policy was common and applicable
to all Samsung msm8974-devices. Move that common stuff here to
ease maintenance.
Change-Id: I86516adfb1b9c55a6959a7faf4ee424a4b3385c8
* So, uh, it turns out we need to disable booting with all
but 1 CPU core to fix CDMA RIL on klte (and hlte?), so
let's enable full dex preopt so that we don't need to
dex opt after system updates
Change-Id: I6fe57f9dcd1da8245eebd51d61055d6de7ffe6cd
AOSP and mainline are going towards removing old 32-bit binder API support.
64-bit binder is 100% compatible with 32-bit kernel and userspace,
so there is no reason for us to keep using the old solution anymore.
We've switched to new API in our kernel, same thing should be applied to our userspace.
Change-Id: I3c95bd7fbd023c5cb08e856b3a3889c03228e843
As stated in https://android.googlesource.com/platform/build/+/418258c
this is required in O-MR1 since sepolicy now prevents system server from
loading anything from /data making our system extremely slow and janky.
Change-Id: I215ec7ebe95981ef0b953fe938e12b83675795ab
* This is causing an mdss pingpong timeout,
which leads to a kernel panic in mdss
* While we could stop the kernel panic, that
isn't the root cause of the problem
* Remove the offsets as we don't have
proper panel documentation for this
* BUGBASH-953
This reverts commit 603779b03a.
Change-Id: Iec49aebc02c9a01b93f4bf23f34e787b338ea805
* Compare things that are used in hlte, klte, lt03lte, and mondrian
wifi and move the stuff that's truly common to here. This will
greatly ease O bring-up of the child trees.
Change-Id: I8fc5a099a348fa7feb502e3afe9b43df6e22d00b
We now get the qcom-common SELinux policy. Get rid of our old policy
and add back config as we need it, rather than trying to merge the two.
Change-Id: I5ca5098c653f09c7901343d0ae71793f6eb21ab8
-Also clean up code and get rid of warnings.
Clean up from Arne Coucheron works on other samsung wrappers.
-Requires device tree to include a CameraParametersExtra.h
for the specific device.
Change-Id: Icab1b9ec17710861f735a05dcdd87dac932c63c2
