Not sure if you mean time, or GPS being spot on. I haven't paid any attention to time when using GPS. But I have an external one, and it works MUCH BETTER, pretty much what I would call spot on.
However, the last couple times I"ve used it my phone has locked up. I am thinking it is the BT program I am using in order to use the external GPS. What blue tooth program are you using?
Both the time and the GPS location are correct when I use an external BT receiver (Delorme BT-20), but the time is exactly 24 hours off. That could definitely cause drift after initial lock (not to mention cause problems locking in the first place).
I use "Bluetooth GPS Mouse" by Argotronic. There is
also a problem with the Captivate's Bluetooth implementation from what I've read. My bluetooth headphones, gps and obd-ii car scanner tool tend to lock up my handset from time to time. It seems to have a problem with sustained serial data communications over bluetooth.
Bluetooth GPS Mouse seems to be pretty stable as opposed to the other BT programs I've used, I guess you get what you pay for. It's a real hassle to drag around two devices on the off chance of needing directions.
I seem to remember stock AT&T Eclair being pretty good with GPS.
---------- Post added at 08:57 PM ---------- Previous post was at 08:48 PM ----------
can someone explain why temperature would effect the GPS in any way? thanks..
Some electronic components are sensitive to temperature. Temperature changes conductive properties, among other things (for example, metal expands when heated). Heat dissipation could also be a factor. Electronic boards can warp, components can separate from the board or the solder can crack. More likely in this case, it just looks like it's working. I've seen tons of people claiming different things have fixed the GPS. Until I can get a lock in standalone mode, and keep it, I'm not calling it fixed.
---------- Post added at 09:52 PM ---------- Previous post was at 08:57 PM ----------
Seems I wasn't crazy about the time thing, but apparently it has only manifested since 2012 rolled around:
code.google.com/p/android/issues/detail? id=24000
This article is about the Tab, but it looks like it is across the board.
