SUPL-2.0-con-034-1/2 Fail because Emergency-NI
did not check inprogress session
Change-Id: I377955c455830bf3bb7cb7fe05d45c4536dabfbc
CRs-fixed: 2483780
To abort inet receiver thread, an abort
message must be sent explictly to loopback address.
For reciever to receive abort message it must be
open to receive messages on INADDR_ANY and not
just specific IP address.
CRs-Fixed: 2462833
Change-Id: I9ab3266d582bc774655fcabfc086dab33010f7d8
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
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
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
Add directory to be reserved for hal daemon to keep track of
location client sitting on external application processor
Change-Id: I192fb011c786bab1752f0e604b86041a9f4cdc33
CRs-fixed: 2436612
LocIpcRunnable is created only for nonBlocking listeners.
But stopListening would use LocIpcRunnable not knowing if
this is a blocking or nonblocking listener. LocIpcRunnable
is no longer a shared resource between the two threads. We
use a copy of string to keep the needed socket name.
Change-Id: Ib5c57a89f630807d6d03f3fbc698a56b9ffddf4d
CRs-Fixed: 2431397
Consolidate the translation from QMI LOC into one
place in order to minimize traffic
Change-Id: I73c2f25e94544a2b69d4227c63548ef11b6a4d91
CRs-fixed: 2430668
Changes to be made starting in Android Q in the way
that Location requests made by Location clients
other than the Android FrameWork (e.g. Network
Initiated AGNSS clients, modem-based clients such
as MDT) are handled
CRs-fixed: 2397454
Change-Id: Ibb5b9429a1ec1e14ee59d89763d8a78607997615
