• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root GPS.conf fix for LG Volt as of 4/9/2015

Im not sure if the capabilities mean all are enabled based off of total number or you have to add up in order to land on a specific capability.

I'm leaning towards adding in order.

I tried 14, which should be 10 plus 4 to enable msa. I'm going to try 16 next for msb, then I'll try 36 which should be scheduling. I've already tried 37 which should be geofence. I suppose I should try 10 as well for on demand time.

Still unsure why our phone was 31 by default. That only makes sense to me if it means multiple capabilities were enabled, 31 meaning 20 plus 10 plus 1 for geofence, on demand, and scheduling capabilities respectively.
 
I had way better (albeit slightly slower)lock with commenting out all supl stuff (version, port, and server)

It appears the shoddy supl support is causing our GPS to start downloading GPS data then messes up part way through and makes our GPS reset and require a lock again.

After commenting out all references to supl my GPS followed my every move, this was with GPS capabilities set at 17.
 
Sorry, I mean 0x17.

Even in my house I'm getting a faster lock than the stock GPS conf file did while I was outside with no clouds or trees above me.

This is with every setting above except intermediate position is 0 and all supl text is hashtagged out. As well as a hash tag on accuracy threshold.
 
Last edited:
/start file


XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

ERR_ESTIMATE=0

NTP_SERVER=north-america.pool.ntp.org

DEBUG_LEVEL = 0

INTERMEDIATE_POS=0

#SUPL_VER=0x10000

# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x17

#ACCURACY_THRES=1000

#SUPL_HOST=supl.google.com
#SUPL_PORT=7276

LPP_PROFILE = 1

ENABLE_WIPER=1

NMEA_PROVIDER=1

A_GLONASS_POS_PROTOCOL_SELECT = 0x4

VENDOR=SPR
#LGE_TLS_MODE=0
LGE_GPS_POSITION_MODE=0

/end file
 
I'll have to go through this at home on my computer so I can revert back and forth. I applied a couple things and it seems improved. Nice work man. We should get this stickied.
 
It seems the lollipop ROM I'm on isn't doing as well as the 4.4 ROM I was running, might be due to the lack of 4g connectivity and the intermittent loss of even a 3g signal.
 
I'll have to go through this at home on my computer so I can revert back and forth. I applied a couple things and it seems improved. Nice work man. We should get this stickied.

Just incase mods decide to do so; I've edited the original post with the top 4 changes we can make to our original GPS.conf file to improve performance.

Sad that it doesn't really fix the GPS issues on Lollipop, I'm hoping that it is an issue in the ROM development and not that Lollipop will need completely different GPS.conf file values. My guess-tament is that the 4g and signal loss issues being experienced in Lollipop ROMs has something to do with it. Any hiccup in the downloading of GPS data (which takes around 15 min) forces the process to start from the beginning, this could cause a lot of problems when dealing with a sporadic loss of signal and a complete lack of connectivity to 4g/Lte.
 
I tried wiping and doing a restore of my 4.4 deodexed ROM and my 4g wouldn't connect anymore. Even after wiping and flashing the deodex ROM, I still had no 4g, and couldn't even upgrade PRL and profile. The buttons were still there in system settings, just didn't do anything when I pressed them.

I had to revert to zv3 via LG flashtool to get my 4g connectivity back.

Even with no 4g coverage, my phone's GPS still locked on and followed me very well (on the restored deodex 4.4 ROM)

Just an fyi, flashing the CM unofficial Beta may cause a loss of 4g/lte connectivity, and the GPS is probably borked as well.
 
This seems to work for me on the latest build of lollipop (3/10). Before my gps wouldn't get a lock at all. My 4g works. Overall it's much better than what I had before.
 
I tried wiping and doing a restore of my 4.4 deodexed ROM and my 4g wouldn't connect anymore. Even after wiping and flashing the deodex ROM, I still had no 4g, and couldn't even upgrade PRL and profile. The buttons were still there in system settings, just didn't do anything when I pressed them.

I had to revert to zv3 via LG flashtool to get my 4g connectivity back.

Even with no 4g coverage, my phone's GPS still locked on and followed me very well (on the restored deodex 4.4 ROM)

Just an fyi, flashing the CM unofficial Beta may cause a loss of 4g/lte connectivity, and the GPS is probably borked as well.
I tried that revert back to zv3 I still don't get lte . I'm going to try again
 
This seems to work for me on the latest build of lollipop (3/10). Before my gps wouldn't get a lock at all. My 4g works. Overall it's much better than what I had before.

I'll have to give that one a try then, I was on the Feb 25th version because I actually like the buttons on the screen as it helps me navigate through apps and screens and recent apps faster than trying to find the hardware keys in the dark after the background light has faded.

My lack of GPS on lollipop might have been due to another glitch I've noticed about our (or at least my) phone. It doesn't like more than one GPS test app installed and running. If I install GPS status and also GPS test, it will work really well for a few min then freeze up my GPS. If I have zero or one GPS test app installed, my GPS works fine.

Might have something to do with permissions of the gps. Conf file. Not sure, just gonna stick to one app for now.
 
I found these from another LG phone user, testing it out now, along with a supl cert file and supl enabled in my GPS.conf

These seem like they are meant to make supl and xtra data perform better by stopping the restart function when the data transfer is interrupted.

Will report on how well it works soon.

################################
# EXTRA SETTINGS
################################
LGE_GPS_POSITION_MODE=standalone
LGE_XTRA_AP_TRIGGER=0
LGE_XTRA_NOTIFY_DOWNLOAD=1
LGE_XTRA_IGNORE_NETWORK_STATE_CHANGE=1
LGE_XTRA_COMPLETE_DOWNLOAD_BEFORE_POSITIONING=1
#LGE_XTRA_NOTIFY_STATE=1
LGE_XTRA_NOTIFICATION_DURATION=0
LGE_XTRA_NTP_RETRY=0
LGE_XTRA_DATA_RETRY=0
LGE_XTRA_DOWNLOAD_INTERVAL=24
LGE_XTRA_INTERACTIVE_TEST=1
LGE_XTRA_CUSTOM_TIME_SERVER=0
LGE_XTRA_ALLOW_FIRST_NETWORK_STATE_CHANGE=1
LGE_XTRA_ALLOW_SPECIFIC_TIME_XTRA_DOWNLOAD=1
LGE_MPCS_AGPS_FLAG=1
 
I'll have to give that one a try then, I was on the Feb 25th version because I actually like the buttons on the screen as it helps me navigate through apps and screens and recent apps faster than trying to find the hardware keys in the dark after the background light has faded.

My lack of GPS on lollipop might have been due to another glitch I've noticed about our (or at least my) phone. It doesn't like more than one GPS test app installed and running. If I install GPS status and also GPS test, it will work really well for a few min then freeze up my GPS. If I have zero or one GPS test app installed, my GPS works fine.

Might have something to do with permissions of the gps. Conf file. Not sure, just gonna stick to one app for now.
I used maps to drive 130 miles to a place I'd never been before and it worked perfectly. All the turns were dead on.
 
I used maps to drive 130 miles to a place I'd never been before and it worked perfectly. All the turns were dead on.

Awesome, I much prefer the lollipop ROM over the 4.4, I love the drop down screen and the speed and responsiveness. The gps.conf file I saw after first flashing the CM 12 unofficial ROM seems like it's made for a device in Germany, and there were a lot of values in it that are in another file on our devices (like izat.conf and sap.conf)

I'm going to give lollipop another run today with the latest build, I have some more GPS.conf values I want to test out.

Thanks for testing out the values, I'm glad your phone still worked after using them :)
 
Running the latest build of CM 12, I have a better 4g signal now than I did with the 4.4 ROMs, and my GPS is following me very well.

This is the GPS.conf I have settled with and have been getting the best ttfl and overall performance.

/begin GPS.conf

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

ERR_ESTIMATE=0

NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org
NTP_SERVER=us.pool.ntp.org
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org

DEBUG_LEVEL = 5

INTERMEDIATE_POS=0

CAPABILITIES=0x37

LPP_PROFILE = 3

NMEA_PROVIDER=1

A_GLONASS_POS_PROTOCOL_SELECT = 0x4

VENDOR=SPR

LGE_GPS_POSITION_MODE=0

/end GPS.conf
 
OK, I tried to set mine up the same as yours. There were some other settings in there that I didn't delete though. Wanted to get your opinion on it as I haven't done nearly as much research as you on this.
Here's my conf file:
Code:
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org

NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

ENABLE_WIPER=1
#LGE_TLS_MODE=0
LPP_PROFILE=3
DEFAULT_AGPS_ENABLE=TRUE
A_GLONASS_POS_PROTOCOL_SELECT=0x4
CAPABILITIES=0x37
C2K_HOST=c2k.pde.com
INTERMEDIATE_POS=0
ERR_ESTIMATE=0
LGE_GPS_POSITION_MODE=0
C2K_PORT=1234
DEFAULT_USER_PLANE=TRUE
NMEA_PROVIDER=1
DEFAULT_SSL_ENABLE=FALSE
DEBUG_LEVEL=0
CURRENT_CARRIER=common
ENABLE_WIPER=1
ACCURACY_THRES=0
NMEA_PROVIDER=1
VENDOR=SPR
As for the arrangement, I didn't think it mattered much, but the layout was written by Faster GPS, which I used to make most of the changes except the extra NTP servers.

I also assumed that the debug level being set to 5 was because of your testing and didn't have anything to do with accuracy.
 
Last edited:
OK, I tried to set mine up the same as yours. There were some other settings in there that I didn't delete though. Wanted to get your opinion on it as I haven't done nearly as much research as you on this.
Here's my conf file:
Code:
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org

NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

ENABLE_WIPER=1
#LGE_TLS_MODE=0
LPP_PROFILE=3
DEFAULT_AGPS_ENABLE=TRUE
A_GLONASS_POS_PROTOCOL_SELECT=0x4
CAPABILITIES=0x37
C2K_HOST=c2k.pde.com
INTERMEDIATE_POS=0
ERR_ESTIMATE=0
LGE_GPS_POSITION_MODE=0
C2K_PORT=1234
DEFAULT_USER_PLANE=TRUE
NMEA_PROVIDER=1
DEFAULT_SSL_ENABLE=FALSE
DEBUG_LEVEL=0
CURRENT_CARRIER=common
ENABLE_WIPER=1
ACCURACY_THRES=0
NMEA_PROVIDER=1
VENDOR=SPR
As for the arrangement, I didn't think it mattered much, but the layout was written by Faster GPS, which I used to make most of the changes except the extra NTP servers.

I also assumed that the debug level being set to 5 was because of your testing and didn't have anything to do with accuracy.


c2k is just another version of supl, I have taken out all references to supl. Even if c2k was working, that's not the correct port for it, not sure why so many gps.conf files come with that text in there like that. For supl to work properly you will need an appropriate supl.cert file and I don't have a Linux machine to create one for our specific device so any of the ones we can download aren't for our phone and therefore won't work properly. It's a matter of how the file is saved on our phone versus how we get it when we download the appropriate one for our devices. I might set up my office pc with a Linux partition so I can dink around with making one for our phone, but all it would do is make our GPS transmissions more secure. I'm not really worried about a hijacker intercepting my GPS requests and sending me false coordinates. I'd like to get it working eventually though just for the nerd points.

You have 'intermediate position' set to '0' which is off, but then have 'accuracy threshold' set to 0 as well, which means to accept all positions. You can put a 1 after intermediate position to get your GPS app to 'find' you sooner, as it will begin reporting your position before a full lock, but the 'accuracy threshold' set to 0 is going to allow ALL positions to be reported to your GPS app, whereas if you set an accuracy threshold of 5000 or smaller (I've seen as low as 80), only the positions within that accuracy threshold will be sent to your GPS app (whether it's GMaps or Ingress or Waze, etc).

The three "Default" lines (the "AGPS, USER_PLANE, and SSL_ENABLE) are related to supl as well, so I got rid of them. This is also why I have changed to LPP profile 1 instead of 3. 3 is to enable control plane and user plane, 1 is just to enable control plane, which is what the other codes are asking our gps to use (such as 'glonas' set to '0x4' and 'capabilities' set to '0x37')

You are correct about the debug level, it is just so I can get a full report on what is happening with my GPS.

Here is the gps.conf I have settled on:

Code:
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra1.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra3.bin
ERR_ESTIMATE=0

NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org
NTP_SERVER=us.pool.ntp.org
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org

DEBUG_LEVEL = 5

INTERMEDIATE_POS=0

CAPABILITIES=0x37

LPP_PROFILE = 1

NMEA_PROVIDER=1

A_GLONASS_POS_PROTOCOL_SELECT = 0x4

VENDOR=SPR

LGE_GPS_POSITION_MODE=0

Sorry if you saw this post pre edit, I had to fix some formatting that copied over and made a bunch of html code get in the middle of my gps.conf info. The above is how it looks in my phone's gps conf. LPP profile 3 or 1 doesn't matter as long as you don't have any supl info in your gps conf file.

It appears that ntp and xtra servers do what supl would do if we enabled it. They all are related to "TTFF" or time to first fix; how long it takes your gps to lock for the first time. They all attempt to speed up the process by supplying information to a server then having our phone contact that server via or 3g or 4g/lte network to download the data faster rather than waiting up to 15 minutes for the 50k/sec transfer of data directly from the GPS satellites. Enabling supl, and xtra, and ntp, is sort of like getting three mechanics to work on your one engine at the same time; it might cause more problems than it fixes.
 
Last edited:
Thanks for the breakdown. The accuracy threshold, according to faster gps, only relates to the intermediate position setting. Since that is disabled, I just left it on the default 0. In your last post, LPP profile was set to 3, I will change it to 1. I had no idea what the c2k stuff was. I'll drop it out too. Thanks again. :)
 
Thanks for the breakdown. The accuracy threshold, according to faster gps, only relates to the intermediate position setting. Since that is disabled, I just left it on the default 0. In your last post, LPP profile was set to 3, I will change it to 1. I had no idea what the c2k stuff was. I'll drop it out too. Thanks again. :)

No problem, and you're right about the accuracy threshold being related to the intermediate position, but a 0 doesn't mean off, if you want off on that value you need to hashtag it (or delete the line all together)
 
I'm still curious why we have http in front of the xtra servers but not the ntp servers, I'm going to try pinging them and see if it matters one way or the other. I know the xtra servers downloaded data with the http in front of them, I didn't try any of the ntp servers yet though.
 
Back
Top Bottom