CRs Change ID Subject
--------------------------------------------------------------------------------------------------------------
974961 I3c8b8ba97c5b2eafa7337d580681044b973c5bea Additional Position Prameters in position report
Change-Id: I43fde64123dfaa2b93fb0630418f74ce0e0e2ad8
CRs-Fixed: 974961
Currently only $GPGSA was being generated for GPS satellites.
This change adds $GNGSA for GLONASS satellites as well.
Change-Id: I7ab0e92c7ed4ce73be11909eefe0d570a1a0fc1e
CRs-Fixed: 978745
Currently only $GPGSA was being generated for GPS satellites.
This change adds $GNGSA for GLONASS satellites as well.
Change-Id: I7ab0e92c7ed4ce73be11909eefe0d570a1a0fc1e
CRs-Fixed: 978745
The current share() and drop() calls are not thread
safe, which can cause memory heap correuption. This
changes the read / write ops to be atomic.
Change-Id: Ic241d4573bdf2e58c4e264e97bd41b56f882c791
CRs-Fixed: 975372
The current share() and drop() calls are not thread
safe, which can cause memory heap correuption. This
changes the read / write ops to be atomic.
Change-Id: Ic241d4573bdf2e58c4e264e97bd41b56f882c791
CRs-Fixed: 975372
carrier specific SUPL_MODE is not updated upon sim card insert.
gpc_conf must be updated with the new value for config to be
updated.
Change-Id: I2a5f10fa7d27be9253e9ca6f34c0c886285d1b11
CRs-Fixed: 953942
The current share() and drop() calls are not thread
safe, which can cause memory heap correuption. This
changes the read / write ops to be atomic.
Change-Id: Ic241d4573bdf2e58c4e264e97bd41b56f882c791
CRs-Fixed: 975372
CRs Change ID Subject
--------------------------------------------------------------------------------------------------------------
940557 I4cbde8d3c49ef4ac287d34a88ea25787b507cdbe Add the support for geofence dwell
Change-Id: Ifb4049c0a7d81093caf8a83277abba90fc394ac8
CRs-Fixed: 940557
NMEA Strings should introduce the sub milli sec part in the
relevant NMEA Strings for NHZ Sessions
Change-Id: I9bac4caa26e87741e5e82e16a8047af20ac8012b
CRs-Fixed: 951144
CRs Change ID Subject
--------------------------------------------------------------------------------------------------------------
881265 I3c895adc2ce1cef36032a25e3c6fd63e70350607 encode field separator characters
923601 Ib6bf917f84d1224e296e91b4fb33b41d6e2c2531 Add support for dynamic TBF updating
935146 I9c3f970aa0f0ca0805fdc2e04aa809329b6a2676 Xtra client always reports carrier as 'unknown'
951144 I9bac4caa26e87741e5e82e16a8047af20ac8012b Sub milli sec part in the relevant NMEA Strings
Change-Id: Iddadd149330bf1bebcdae8fb3a65d8aca93278b4
CRs-Fixed: 923601, 935146, 881265, 951144
Replace all separator characters ('/','+','|','%') in the raw string
by their corresponding encodings (%2F","%2B","%7C", "%25")
Change-Id: I3c895adc2ce1cef36032a25e3c6fd63e70350607
CRs-fixed: 881265
The problem was caused by populating the carrier upon phone bootup
when the the property maybe not initialized yet. This module is
updated to remove the populating code of carrier in phone bootup.
Change-Id: I9c3f970aa0f0ca0805fdc2e04aa809329b6a2676
CRs-fixed: 935146
enhancedIOD parameter in QMI needs to be added to HLOS driver
structures, and appropriate fix in structure members
Change-Id: If89de03ff69fabb3d57a7b7dafe957eb73302794
NMEA Strings should introduce the sub milli sec part in the
relevant NMEA Strings for NHZ Sessions
Change-Id: I9bac4caa26e87741e5e82e16a8047af20ac8012b
CRs-Fixed: 951144
This change adds the support for checking
if modem support dynamic TBF updating.
Change-Id: Ib6bf917f84d1224e296e91b4fb33b41d6e2c2531
CRs-Fixed: 923601
NMEA Strings should introduce the sub milli sec part in the
relevant NMEA Strings for NHZ Sessions
Change-Id: I9bac4caa26e87741e5e82e16a8047af20ac8012b
CRs-Fixed: 951144
Currently Location HAL forces TBF of 1 second or larger
even though ALM permits lower values. GPS HAL shall have
smaller limits as Modem code actually controls minimum
TBF value
Change-Id: I4a2bbd51da34e441f148275ec3c2c4fa9ece7599
CRs-Fixed: 951152
GPGGA/GPRMC/GPGSA can be reported two times per
second in some cases where we lose all satellite
signals. We should report these NMEA sentences only
from position report to prevent this.
CRs-fixed: 884484
Change-Id: I123d9f074ca725703c6e90397160b701033e22f0
To prevent reading beyond the length of
the buffer that contains XTRA data, a
check has been introduced assuming an
approximate limit for the size of the
data
Change-Id: I7e05beadec76c3308448b9198fd23c8e8b97394d
CRs-fixed: 420623
GpsLocation memory will now be cleared inside the
Loc Api handler itself, so no need to do it a second
time before calling into the Loc Api handler.
Change-Id: Iec37624621d6eb4806eb8e13c807bb4e40584e39
CRs-fixed: 726800
GNSS Measurements and Polynomial reports need to be enabled
only when AP DR (EXTERNAL_DR_ENABLED=1) is enabled
in gps.conf
Change-Id: I13437d997e96a6403923d49f62f1e7c2f70e9c04
CRs-Fixed: 937944
LocTimer on timeout would currently delete timer delegate.
This meddles into the management of LocTimer::stop() call,
and the order of obj delete needs to be synchronized in a
few different places as a result.
This change lets the delete of the timer delegate obj fold
into the stop() handling, which would be easier to synch.
Change-Id: Ic3e0b3d183dceb9e6e2db4c47ec9d6e296b0c3f6
CRs-Fixed: 916590
Removed tCreate and tAssociate from MsgTask. LocThread
now can optionally take a tCreate method. Associator is
replaced with *firstMsg* option to MsgTask, which is a
more generic option, that can associate or do other set
up job at the create of a MsgTask.
The current MsgTask doesn't use tCreate, which exposes
a slight time window for Location HAL when its MsgTask
is NOT associated to DVM heap but a message delivery to
DVM could be attempted during this time.
Change-Id: Iafd5b91b693baacb9b7064463f8c44f74026f54c
CRs-Fixed: 902350
when a ticking timer is stopped, currently kernel doesn't
get updated with the next immediate timer's interval. As a
result, kernel timer will expire sooner (with the stopped
timer's interval), and the next timer's client is notified
for this expiration.
Change-Id: I0d67d1418cb9bfe7f70ae71252901d4c6bb699b3
CRs-Fixed: 909776
LocTimer::stop() can be called from different threads, which must
be protected. Currently there is a race condition between back to
back stop()'s or expire() + stop() events.
Change-Id: Iae80b78f049a32da87639f813c6f5126b4ccd072
CRs-Fixed: 904627
BOOTTIME_ALARM and BOOTTIME were added to timerfd_create
in kernel version 3.11 and 3.15 respectively.
But for targets still on older kernel version we fallback on MONOTONIC.
CRs-Fixed: 897805
Change-Id: I47d9780d69ce5ee8c183c84baa93ea3c1a00db57
LocTimerWrapper implements loc_timer_start/stop calls for backward
compatibility. There is a race condtiion where the wrapper object
could be deleted by the client thread and expireation handling at
rough the same time, which would have the memory freed twice. Now
they are mutext protected.
Change-Id: I25d7466db88a840a8a09e7a476cface48c91d22e
Timer must be removed from epoll as soon as it expires,
otherwise it continuously expire. Current timer removes
from a different thread, this triggers repeated expire
events until the maintain thread gets to remove it.
Change-Id: Ie523bce5069416521d49bc0178d2cad2dd1f04da
CRs-Fixed: 870568
LocHeap, LocThread, LocTimer, and moved MsgTask to
utils. Also added are LocRankable and LocRunnable
abstract classes.
Change-Id: I76975455d24f2c84a95dcc1b04f79fea562ea5ba
CRs-Fixed: 855222
