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
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
Added dlGetSymFromLib() to provide a utility that dlopen()'s
a library, and get the pointer to a symbol name.
Change-Id: I770eaef18a61aaa458833b3ca778f44b299585f5
CRs-Fixed: 2404939
Remove GTP-WAA and GTP_AP_CELL feature as GTP will
support only third party GTP WIFI and legacy GTP
WWAN solution.
CRs-Fixed: 2384327
Change-Id: Id3613bde1716542027978af30084f5e997f28b00
(1) In location data struct, change size_t to uint32_t as size_t
is machine dependent and can not be sent as part of payload
to the other processor.
(2) Change LocIpc ifdef to match with the file name
Change-Id: Ia3f029641106a547e18904be1e3fb56ec09de569
CRs-fixed: 2367517
Enable support for build on External AP without
libcutils or any Android library support.
CRs-fixed: 2368435
Change-Id: I978127348fd6b8d90ed5ef0a714c02437dc59ee0
1. KlobucharIonoModel
2. Additional parameters for Glonass
3. Add gps system time to ephemeris reports.
CRs-Fixed: 2388931
Change-Id: Ibd08496c8eda2ce7571cbdd71ff0c179f7376aa7
Some vendor enhaced processes are not to be launched only if this
is not a vendor enhanced produce. Condition incorrect.
Change-Id: Ieb520d77500f78968cb78b69169b068356f880ab
CRs-Fixed: 2392220
(1) revise struct of GnssSvMeasurementSet so it can be used
to send only valid SV measurement via IPC
(2) remove reference to COMPASS system, as COMPASS named is
replaced by BEIDOU system
(3) correct typo in GNSS_GLOS_MSEC_VALID to GNSS_GLO_MSEC_VALID
CRs-fixed: 2337832
Change-Id: I325346fa414e3a94422cb8ab4cc5b77d6efaf485
startListeningBlocking is meant to be called under a reader
thread, which is the case if startListeningNonBlocking calls
it. A LocIpc client may delete the LocIpc obj, which would
trigger sending an ABORT msg to the reader thread before it
is subsequently deleted, in which case, it is possible that
when the reader thread comes around to process the ABORT msg,
referencing the data members of the possibly stale obj would
cause unpredictable behaviors.
Change-Id: I441af85c04d92b6fff695c020e3e0b4bd5e90409
CRs-Fixed: 2380093
startListeningBlocking is meant to be called under a reader
thread, which is the case if startListeningNonBlocking calls
it. A LocIpc client may delete the LocIpc obj, which would
trigger sending an ABORT msg to the reader thread before it
is subsequently deleted, in which case, it is possible that
when the reader thread comes around to process the ABORT msg,
referencing the data members of the possibly stale obj would
cause unpredictable behaviors.
Change-Id: I441af85c04d92b6fff695c020e3e0b4bd5e90409
CRs-Fixed: 2380093
Only first 3 chars of thread name were getting set
because of incorrect length check. This change fixes the issue.
CRs-Fixed: 2376235
Change-Id: Iba4ad44af2e3bfde8da8ae4efdd4b132299ae9b7
