Earlier this identification was done in loc.cpp
This change moves that to a separate utility.
Also included is a change to not return
a handle to the GPS interface if the target
is found to be MPQ8064.
CRs-Fixed: 418009
Change-Id: I98d5619d2e6e63711a9b56f0af2b3ddd27372871
Locking the slot mutext during a loc_ioctl call
can cause deadlock in some rare cases.
Change-Id: I09aa2ad7c67c326fee90447db960895d7f1fb149
CRs-fixed: 412208
As a security measure, callbacks
are checked to make sure they are
not NULL pointers.
Change-Id: I391e1cc373e8098449303709d8d1b67d305fb633
CRs-Fixed: 404438
This fixes the problem that GPS doesn't work until reboot after modem reset.
Bug: 7216911
Change-Id: Ibfee6a28850490548da2e0ccaefdabe9b826b5e9
Signed-off-by: Iliyan Malchev <malchev@google.com>
Disable coarse position injection from GPS HAL when XTWiFi
Network Location Provider is in use. This is needed to avoid self
learning loop inside modem.
Change-Id: I0526317221d3490c41d0d8d901fbfa4d93e9a0b0
CRs-Fixed: 409409
Instead of having a switch case that sets bits in the
lppconfig mask, the mask is assigned whatever value
was read from gps.conf. The advantage of this being
that if in the future additional bits are added in
lppconfig, there need not be a code change; only
comments in gps.conf have to be updated to inform the
correct value for those additional bits
CRs-Fixed: 406969
Change-Id: I979151b44cd85e98b59b4586fdd49e20a7d7c82b
Previously, modem's request for NTP time was not supported.
This change enables that request to be serviced through the HAL
and current NTP time is injected into the modem
CRs-Fixed: 406357
Change-Id: I471f98cf57a276902d7991da48cf7244fe798318
this is to support bringup efforts. This change will decouple
the dependencies between GPS HAL and proprietary QMI headers,
so that we can build HAL without any proprietary repos.
Change-Id: I7b836d09f4ac6b1a1bdb38f8d6a2bfb90bb5bf01
Changes to assign the correct permissions for 'gps" group for
Rx path from HAL to BIT daemon
Change-Id: I6c5dc4ff0a1379a95888f4d98e88f0174a7a2a79
CRs-Fixed: 400339, 387672
The id for apq8064 v2 is 153 vs apq8064 v1
id of 109, so the id can be either in order
to conclude that the device is apq8064 so
that GSS can be launched.
Change-Id: I8126854f18ba30a1fe46992993185266e9d1db18
CRs-fixed: 405494
AgpsStatus added with a couple string fields for wifi
which are not NULL ended when they are not used. This
get passed to AFW JNI, and allow UTF8 string with the
open ended buffer with junks in it. It might cause
exception depending on the content of the garbadge.
CRs-Fixed: 405473
Change-Id: If762748a4c63fe1be59491b5d08dbadd479176b3
The current cleanup mismatches agps_init(), so that it the agps state
machines will get deleted in the cleanup but never get recreated next
time apgs_init() is called.
Bug 7216641
Change-Id: Iddba9fd0d90c790e658f14c42c8a25d22b8749c0
Since modem does not consistently send
SESSON_END/ENGINE_OFF event, always report
SESSION_END on stop gps and SESSION_BEGIN on
start gps so that the icon is turned on/off
correctly.
Bug 7185242
Change-Id: Ib3954529056a653d7057aedb489be1ccee9eaf1d
Since modem does not consistently send
SESSON_END/ENGINE_OFF event, always report
SESSION_END on stop gps and SESSION_BEGIN on
start gps so that the icon is turned on/off
correctly.
CRs-fixed: 401664
Change-Id: Ib3954529056a653d7057aedb489be1ccee9eaf1d
The current cleanup mismatches agps_init(), so that it the agps state
machines will get deleted in the cleanup but never get recreated next
time apgs_init() is called.
Bug 7216641
Change-Id: Iddba9fd0d90c790e658f14c42c8a25d22b8749c0
Since modem does not consistently send
SESSON_END/ENGINE_OFF event, always report
SESSION_END on stop gps and SESSION_BEGIN on
start gps so that the icon is turned on/off
correctly.
Bug 7185242
Change-Id: Ib3954529056a653d7057aedb489be1ccee9eaf1d
