[haggertk]:
* During bring-up of O, GPS was exhibiting different behavior from
N -- an appropriate number of satellites would immediately lock,
but a fix would not resolve for 30-90 seconds. Digging up this
change from the L-era allows GPS to resolve a fix in a nominal
amount of time.
Change-Id: If9fd67483fedee915d46f7b9d2a7e0851400de3c
The current logging macro always uses LOGE, which is
confusing to external developer looking at our logs.
Also changed LOC_LOGx definition to follow the same
syntax as that of LOC_LOGX.
Bug: 29499503
Change-Id: I803233a9d0b241bf9aeb2ee0d4bd2e7cc52ed75b
CRs-Fixed: 1113702
Explicitly add liblog as dependency for modules that use Android
logging. Also remove obsolete build flag.
Change-Id: I91a458b44ff34c91a8f6875f5c3e931f620c613a
Removing statement to set LOCAL_CLANG flag explicity to
true. It will be true by default.
Change-Id: I2eaba5a89e64088e3383b962dceaaa7e975e997a
CRs-Fixed: 989476
gps: Correct forward declaration in proprietary definitions
Fix gps runtime error
The qcom prebuilt binary relies on FlpExtLocation_s,
so we cannot change it to FlpExtLocation.
This patch fixes it.
gps: fix remove trailing space
In setXtraUserAgent,
size_t is unsigned and never being negative.
Will cause segmentation fault, if string is all space.
Change-Id: I1cf1f956943b0739640afe909954ade6921e28a1
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
* After two years of warning us, Google has dropped non-inlined
versions of the android_atomic functions. Unfortunately, some
legacy blobs still expect these to be in libcutils.
* atomic.c from system/core/libcutils at c56648948
Change-Id: I31cba78c62b17f045fa912534dd61c8aaaddaaa8
Mondrianwifi does not like having this enabled. When it is enabled,
it causes audio distortion in some games when using a2dp output.
Partially reverts: "Reduce fast track multiplier"
Change-Id: Ic50bb016275de821be4651280c67c42f64241dab
* The codec performance figures were measured on bacon, and do not match
the performance of the various Samsung devices.
This reverts commit 5e340af2e6.
Change-Id: I7ce0eab3bdd0c89919b3bb29d56a346de587e075
* Qualcomm caused hell-on-earth with libavenhancements- an
apparently well-intentioned effort to minimize the amount of
change in f/av which has backfired. In order to use this
library, an OEM must not change *anything* *anywhere* in f/av
to maintain ABI exactness. And that ABI exactness is different
per SoC branch and constantly in motion. Best of all, the
base classes are monkey patched with a proprietary library which also
is different per SoC branch and much exactly match the f/av
code. And if you get the ABI right, then your customizations
stop working because they've been hijacked by overloading. The whole
message bus is hijacked, and you're wasting your time.
* Now that FFMPEG can talk to all the hardware codecs, there is no
reason to tolerate this. Our stack has more features, more codec
support, and it's open source all the way.
* I love Qualcomm's SoCs, but come on guys.. I expect every OEM
will complain about this AV shit then proceed to gut it as I am doing.
Change-Id: I8ed0de62d64cc10054933cd70a9958ea10359c7a
