the original msg_q_init takes a q handle in the parameter list
which makes it inconvenient for chain statement. This really
adds nothing be making it slightly convenient
Change-Id: I1e7f931d6b278c804ec6f7d87c1a79a3ffcceb75
Check the CAPABILITIES in gps.conf to see if the geofence is
enabled or not. If it is not enabled, the function of getting
geofence interface will return null.
Change-Id: I6500cedd775d83b4701fbe2b3a111c170c8a34be
CRs-fixed: 513494
Changed the communication path from ULP JNI to libulp
engine to avoid the GPS HAL layer. This improves modularity,
removes dependencies and promote easier integration for OEMs.
Change-Id: I6bc883499b8ed3649cfc194038057a19ba2fd4f6
Changes to ensure FLP positioning call flow works
even if GPS is disabled on the Android settings
menu.
CRs-Fixed: 476628
Change-Id: I54b9f9861a14f7c42f45c48e57e9558f14a4de92
The function was returning an error code
which was causing GPSLocationProvider to
fail initialization
CRs-fixed: 501318
Change-Id: Icec707c3b9edc60bd07914b130077f9a96c5e794
GPS-enable gets too heavy at powerup, when loc_init is
synchronous, where loc goes to get the hardware handle
if AP init happens faster than the GPS hardware. The
loc init calling thread is from Android framework, and
it locks a mutex that in turn could lock up system server
main thread upon race conditions.
The second half of loc init, i.e. the reinit, is now moved
to loc worker thread. This should help release some of the
powerup timing pressure on the framework threads.
Added a message just for asynchrous Loc Init so as to execute
init specifically.
Change-Id: I369e461ca4ca61cea3a9729c84d24af4ffa8e51d
CRs-fixed: 472843
Removed FEATURE_DELEXT flag that is no longer
needed after adding the flags for this feature
to gps_extended.h
Change-Id: Id8a095309892e2eb328a02ef17e4aa1b1b54e815
qcom bsp will handle xtra/agps/ni/time through
qcom propreitary service, and non-qcom bsp will handle
xtra/gps/ni/time through android framework.
xtra url will be queried from modem on qcom bsp,
and read from gps.conf from non-qcom bsp.
Change-Id: Ib54a1596caa65f7aa0358f639640c3d1074980e7
When a request to RELEASE ATL finds no
active subscribers, return ATL close
failure
Change-Id: I591d5456d5ce1218cc82bf7ba430176ec4f13174
CRs-fixed: 502024
In accordance to gps.conf, debug level of 0 now
produces no logs at all. In addition, if the
parameter DEBUG_LEVEL is commented in gps.conf,
logs will be printed according to Android's logging
levels
CRs-fixed: 503157
Change-Id: I26ca2be67fbc7ce2bf633f66d9b88ca6450e9d27
The struct was not defined in the
NAME_VAL() format and hence was returning
garbage characters in place of error
strings
Change-Id: Ic59e636c8bf99fe91488c312b83f31c36941c202
Introduced support for handling modem request
to start an emergency call using QMI WDS profiles
or fallback to an ATL request if the call does
not succeed.
Change-Id: I29b617687db0d3f26610bc74f8dc95940574f52d
The function was returning an error code
which was causing GPSLocationProvider to
fail initialization
CRs-fixed: 501318
Change-Id: Icec707c3b9edc60bd07914b130077f9a96c5e794
Position report NMEAs will be generated only
if the position report is a final fix and not
an intermediate fix. Blank NMEAs will be sent
otherwise.
CRs-fixed: 467575
Change-Id: I60e63faf3e4503f5a6ce93211d4017aa7695b78b