[Galaxy S I9000 General] sjdean:
To be honest Im getting quite fed up of people accusing me of saying and doing things I haven't said or done.

Sorry if I offended you. You posted a potential solution. I rooted my phone and tested and posted the reasons why I didn't think it was a working solution, and why I believe the original information was wrong.

You said you have seen the information before but don't understand how it is wrong.

I explained it further, and you accused me of being hostile?

I haven't accused you of anything.

What the? What do you mean, I won't tell you, I told you my results, and given that you can only view secgps.conf through having a rooted phone, I'd take this as a given that I rooted my phone...

Im glad that this "solution" worked for you, but unfortunately we've seen so many "snake oil" fixes in the past, from using Skyhook, to using MS Based connections, changing the SUPL Server, changing the NTP server in gps.conf. Nothing has worked.

We've even seen original firmware work flawlessly for two weeks before giving up the ghost.

At the moment, GPS appears flakey. When one solution works well for one person and not for another, we have to question whether this is actually a fix or not.

For a start, we should ask how they are using and testing their GPS? Are they stood still, are they moving, how fast, are they in a valley, is there a lot of other radio interference? Are they in car? What is the weather, the temperature? Are there tall buildings, trees, how much sky cover? Are they indoors, outside? What software are they using? Was this just a temporary glitch?

I myself use LBSTestMode, GPS Test, GPS Status, GPS NMEA Data monitor, Bluetooth GPS, GPS Refresh, MyTracks, Waze, Cardio Trainer, Sports Tracker and of course Google Maps.

Navigation and route tracking is important to me, and as a developer myself (though not with Android), I have a high commitment to testing and won't sign off on something based on some emotional evidence that I either think it works because I got eight satellites in the corner of my house in 10 seconds.

I'll test in my house, I'll test in the open, under bridges, under trees, in the city, in all sorts of weather, walking, running and driving.

I tried all these solutions. None of them work. I suspect a glitch, something - maybe bad data, locking out the GPS, not utilising A-GPS correctly, not to mention the 20 SnR issue and the 8 satellite lock fix.

Understand users - how many say they get a lock on 10 satellites, when quite clearly, that is impossible under the SGS firmware. They think a lock includes a grey bar in GPS Test.

To answer your question, yes, I rooted my SGS and I posted my results that show that it doesn't matter what is in SecGPS.conf, the Galaxy S maintains its own parallel settings elsewhere for LBSTestMode. You will also see that at times, settings in LBSTestMode do not match SecGPS.conf which proves that SecGPS.conf isn't read in for anything - unless it is used by other programs, but from what I see, SecGPS.conf is a Samsung thing, not an Android thing.

If I can get further into Android, I might take a look through some of the databases and xml files.

Thanks

Simon