RIL_SignalStrength_v10 not support gw.timingAdvance. But default 0 will
be taken as valid value. Set to INT_MAX as invalid value.
Bug: 123096279
Test: Build pass. Correct value for GW timingAdvance in radio log.
01-22 16:22:41.150 1779 1910 V RILJ : [UNSL]< UNSOL_SIGNAL_STRENGTH
SignalStrength:{ mGsm=CellSignalStrengthGsm: rssi=2147483647 ber=99 mTa=2147483647
[haggertk: Upstream commit updated to patch both
convertRilSignalStrengthToHalV8 and convertRilSignalStrengthToHalV10,
as the upstream libril only has a single convertRilSignalStrengthToHal]
Change-Id: I37cc2c246d045a07ffad863fb0cc852d8184c3ca
The index value for GSM/CDMA/IMS application shall be -1 if there is no
relevant application according to the comment written for CardStatus
structure in radio/types.hal, so it shall be initialized to -1.
Bug: 63967442
Test: Confirm that the index values are correctly initialized.
Change-Id: I692e9049145d0f0c3c57879c25d0697879c76b39
Use strlcpy instead of strncpy when copying strings to make sure
the copy is always null-terminated.
Bug:73436938
[haggertk: Our original CAF base had the actual "replace strncpy
with strlcpy" part of this change already. This just adds the
expected sendErrorResponse()]
Change-Id: I12d4883c22a180e2136dc8c85bc0394ddcdcb706
Legacy RIL uses an integer to encode the number of
MNC digits. Because the size is not fixed, leading
zeroes result in ambiguity in the length of the mnc.
This change adds support for passing the number of
encoded digits in the most-significant nibble of the
mnc integer (which is only 10 bits). Thus, on any
implementation that is 16-bits or wider, the mnc info
will be properly encoded and decoded with the
correctly-sized string.
Bug: 111971808
Test: ril::util::mnc::test
Change-Id: I24aeba5328a63f80b0d6b25b068bd19160191dff
* 'lineage-16.0' of http://www.github.com/LineageOS/android_device_samsung_msm8974-common:
msm8974-common: gps: Correct week rollover timestamps
msm8974-common: gps: Fix race condition when GPS app is closed around an SSR event
msm8974-common: gps: Adding fix for KW warning
msm8974-common: gps: Assure event mask is set properly to get positions
msm8974-common: gps: Fix unable to clear existing event bitmasks
msm8974-common: gps: Add tech_mask in UlpLocation to support report
msm8974-common: gps: NMEA report indication to ULP
msm8974-common: gps: Making SUPL ES run time configurable
msm8974-common: gps: Fixes SUPL_MODE
msm8974-common: gps: Consider nsec while ranking the timer objects
msm8974-common: gps: Adding a new NMEA sentence : $GNGSA.
msm8974-common: gps: Set correct target for msm baseband
msm8974-common: gps: Add Cleanstep.mk
Change-Id: Ibfdb99e86d3bc3829b565ee8732a7a399ff27915
This adjustment will help with applications checking the time coming from gps.
Some applictions will consider times in the far past as an error.
Change-Id: I69d6971249c4898ac3895f725e46f268cdb2b00d
Fix race condition to get avoid stuck in modem if GPS application
is closed right around a SSR event.This fix will prevent resume the
session once HAL loc_stop has been called.
Change-Id: I4e5c3f09c097b835d8a685a8b465eb86dd06cd7a
CRs-Fixed: 1058559
Fix for buffer overflow possibility for the thread name passed in to
pthread_setname_np() method.
Change-Id: Id323dd058eddcf50d6fd9ec8908e9997b30c561b
CRs-Fixed: 999457
The event mask can be retrieved in the context of
client thread as zero and then queued up to go to
msg task thread. By the time the msg is actually
handled in msg task thread, the actual event
mask at LOC API layer may have already changed, but
this mask would then be overridden by zero. This
can cause no modem events to ever come, including
position reports.
The fix is to not retrieve the event mask in the
client thread, but instead wait for msg to be
handled in msg task thread before retrieving it.
Change-Id: I48562d028bbfa187732686c060b5cdd62c6d5a89
CRs-fixed: 2219519
Fix for an issue updateEvtMask call chain is
unable to clear existing event bitmasks stored
in LocApiV02.
Change-Id: Id34e2d92a506e7300f3d9b3ec74a80a1f6822787
CRs-Fixed: 2085379
SUPL ES gets updated as part of the sim specific
AGPS config hot swap update. We keep that lastest
SUPL ES and send that as part of the NI request,
to let NI handler to know the config status.
Change-Id: I566725d5db9b3abdbd9a423b86c10b819217f4f6
CRs-Fixed: 1024879
Carrier specific SUPL_MODE is not updated upon sim card insert.
gpc_conf must be updated with the new value for config to be
updated.
Change-Id: I2a5f10fa7d27be9253e9ca6f34c0c886285d1b11
CRs-Fixed: 953942
Currently only $GPGSA was being generated for GPS satellites.
This change adds $GNGSA for GLONASS satellites as well.
Change-Id: I7ab0e92c7ed4ce73be11909eefe0d570a1a0fc1e
CRs-Fixed: 978745
* This served a purpose for a period of time, but we decided to embed
the relevant symbols directly into libril.so with 8f6082f
This reverts commit 61a18ade33.
Change-Id: Ifb92a32be007fd0f842af38cf652edffde0604e5
Not needed in Q, as scanning works without it, and the feature
hasn't been forward ported.
This reverts commit 881a6b9fff.
Change-Id: Ida4d2ef429cef47178c9858082dbaae8c1207716
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
