When qrtr socket receiver has restarted, need a way to inform
sender so sender can restart the service discovery process
Change-Id: Id665da649e0962691277124b42f1ee9cc6160fa8
CRs-fixed: 2445555
(1) Add support to report out calibration confidence in position
report
(2) Update gps quality of GGA, mode indicator for GMC and VTG
NMEA sentences
Change-Id: Ia1aa5283deffed6638172b90a41b481c2d199229
CRs-fixed: 2438838
loc_service_mask should not be populated with any
SAP(Basic or Premium) value if the SAP value is
MODEM_DEFAULT.
Change-Id: I665bb90e4a814dc31bed566cc0b2ecffcfae52ac
CRs-Fixed: 2457874
Redesign the inet sender and receiver to
be able to accomodate udp and tcp types into
one base class.
CRs-Fixed: 2429102
Change-Id: Ie138839a5c8842813c99053816e06e4ed7f6b314
Move basic location info to top so if a new field is added to
GnssLocationInfoNotification, it will not impact the basic
location info.
Change-Id: I362ee0f6f09c10e3df64ed6993b73a256690c38d
CRs-fixed: 2468348
Qrtr and Qsock bot have createLocIpc*Sender and Recver
APIs in LocIpc. But Qrtr is really next gen of Qsock.
The two will not co-exist. Their existence depends on
kernel versions, i.e. 4.9 and earlier is Qsock; while
4.14 and later is Qrtr. Having 2 sets of APIs doesn't
make sense, as client would have to know what are the
right ones to use, which there is really only one set
of backing implementations.
Change-Id: Ia473f282bb271ae213d7dc5020b0b8c7b0a8cb8f
CRs-Fixed: 2466857
Cross processor communication needs explicit sized structures.
Avoid using platform defined values like size_t which may
vary from 32-bit to 64-bit.
Also use explicitly defined timespec32_t structure that will
only use uint32_t fields.
CRs-Fixed: 2428163
Change-Id: Ida72f53ac672d9c9b86879bb9861cecefe6f8c6d
We want to avoid reporting locations to AFW while
measurements is active but tracking is not active.
Change-Id: Icbb581199e6f5eba3cfe81cb6ab39337bb7ea51a
CRs-fixed: 2441384
On cleanup, the locApiStopTracking is called regardless
if a session is active or not, where this error would
be printed. This is an expected case, so it should not
be an error print.
Change-Id: Ieb10d159ad61a212821ef897d50d635354557cca
CRs-fixed: 2461760
Register HEALTH Hal client in all Gnss Hidl impl
to acquire charger indication.
Change-Id: I3fcc00dd14a95e2375ab27a8c84c260300f9e90d
CRs-fixed: 2411445
gnssConfigRequested in setConfigCommand handling currently gets
data into gnssConfigRequested in LocApi thread. This introduces
race condition that adapter.getAfwControlId() could be called
from a different thread than where adapter.setAfwControlId() is
called.
CRs-fixed: 2453439
Change-Id: I75ce482a4a87436dff04972ffd82b48db3af62c1
- Fix a Use After Free issue in Gnss Update Config
If Engine Capabilities are not known yet at the time
of the MsgGnssUpdateConfig, the ids arrray will be freed
but the ids pointer will be copied into a new
MsgGnssUpdateConfig that will access the ids array again
- Issue in NetworkInfoDataItemBase which will result in
array out of bound access which might result in heap
buffer overflow.
Change-Id: Ib5a6dc29fef9eb6676d4605f92d60f26a47d1d90
CRs-fixed: 2449980
LocIpc now doesn't have any impelementation of sockets,
but a framework that provides threading for any sockets
that can be wrapped into LocIpcSender and LocIpcRever
APIs.
Also updated XtraSystemStatusObserver to using the new
LocIpc and LocIpcLocalSender and LocIpcLocalRecver.
Change-Id: I506c77198f9ce1e7d4dfd5e596dc0ac21d928e34
CRs-Fixed: 2443124
