The canonical location of the HWASAN runtime, an LL-NDK library, is being moved
to the runtime APEX. It is apparently the first LL-NDK library in the runtime
APEX that does not require a legacy symlink in /system/${LIB}. Therefore we
need to add the runtime APEX's ${LIB} directory to the various search paths
used by the linker so that the library can be loaded from the default and
sphal namespaces.
Bug: http://b/134459232
Test: Builds
Change-Id: I1f63e1a2a61e1717d00736ef431f3ec2a9334193
Merged-In: I1f63e1a2a61e1717d00736ef431f3ec2a9334193
(cherry picked from commit 61f5fdf5c907f83f777395b7ebd45432855b5e7b)
* Legacy devices do not have vndk-sp, so we have to add
/system/{LIB} to sphal search paths to make sure linker
can find the according libraries successfully.
Change-Id: I95b4b4cc9b187ce2b3a50e4e4d1e4940f36e087d
* This config needs to be modified for legacy devices. As
there is no easy way to split it, import it into device
tree and bind mount it instead.
* Head at android-10.0.0_r2
(3ac371484399da6efbd0c835aa461d3326263ab1).
Change-Id: I8d5003d7cd3a471c569844aede4b5ea4c68ae36b
In Q, this looks like it's making the system wait for a
specific widevine service, which we don't have.
Removing this appears to make L3 start working again.
Change-Id: Ib410029519e1d3cb0f0f3a5aa553976b36bca8c3
* Even though the stock gps_debug.conf says that you put
customization in fw/b overlays, Q doesn't look to those anymore.
* With XTRA_SERVERs in those overlays you get:
GpsPsdsDownloader: No PSDS servers were specified in the GPS configuration
This reverts commit 399e9af90a.
Change-Id: Id392cf4a9b91a63a4400e546bc9ba4c32b656ef4
* hlte's copy errors with an ILL_ILLOPC:
Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xaeff97c8 in
tid 10171 (Binder:6108_3), pid 6108 (mediaserver)
* This common copy from G900FXXU1CSA1_G900FVIA1CSC1_VIA does not result
in such an error and is compatible with all Samsung msm8974 devices
Change-Id: I7dd8b31c327b3eadeacdb7be9d43495a7fabb816
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
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as its a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017
Signed-off-by: John Stultz <john.stultz@linaro.org>
Add zero clearing of allocated nmea buffer to ensure
the nmea string is null terminated.
Change-Id: Ie36010a7d3eca16dabb3067ae891a94e4b63b10c
CRs-Fixed: 2041933
* This will contain functions used by the actual extensions at the
device level, it will not be a full-fledged libinit extension on
its own.
Change-Id: I2752dbf7d0b0fb439765fa99b61c82ec10a6c3d2
* We already set props via system.prop, so let's not mix
and match between that and PRODUCT_PROPERTY_OVERRIDES.
Change-Id: I92c6863b8393640e2239decd7f089ee890b3c7f7
* It doesn't make sense to maintain these in the numerous device-
specific trees. It especially doesn't make sense for those to be
subtly-different.
Change-Id: I4e82c0f6b5b835ac4c742a5d5663a8f3498aaf7b
* 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]
