MiPad4/android_device_xiaomi_sdm660-common
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

GPS_LOCK has the wrong value after killing GNSS process

Browse source 
CRs-fixed: 2500864

Change-Id: I5b6cd779ef5c378eedfb54b74b29dbf3191784a1
This commit is contained in:
Mike Cailean 2019-07-30 18:35:42 -07:00 committed by Gerrit - the friendly Code Review server
parent f6586f43a3
commit 818dacd234
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
gnss/GnssAdapter.cpp
View file

@ -1082,9 +1082,8 @@ GnssAdapter::gnssUpdateConfigCommand(GnssConfig config)
if (gnssConfigRequested.flags & GNSS_CONFIG_FLAGS_GPS_LOCK_VALID_BIT) {
GnssConfigGpsLock newGpsLock = gnssConfigRequested.gpsLock;
if (GNSS_CONFIG_GPS_LOCK_NONE == newGpsLock) {
newGpsLock = GNSS_CONFIG_GPS_LOCK_MO;
}
newGpsLock |= GNSS_CONFIG_GPS_LOCK_MO;
ContextBase::mGps_conf.GPS_LOCK = newGpsLock;
/* If we get here it means that the changes in the framework to request for
'P' behavior were made, and therefore we need to "behave" as in 'P'
@ -1102,7 +1101,7 @@ GnssAdapter::gnssUpdateConfigCommand(GnssConfig config)
in this case (return to 'P' code) */
if (mAdapter.mSupportNfwControl) {
// case 1 above
newGpsLock &= ~GNSS_CONFIG_GPS_LOCK_NI;
newGpsLock = GNSS_CONFIG_GPS_LOCK_NONE;
} else {
// case 2 above
gnssConfigNeedEngineUpdate.flags &= ~(GNSS_CONFIG_FLAGS_GPS_LOCK_VALID_BIT);