Cory, People are having better GPS luck with the cold start?
Do we know the technical difference?
[tapatalk on android]
Hey Egghead,
Read this today on Engadget on a post related to issues on the Samsung Epic (sprint's galaxy S phone):
Problem: GPS
Description: The most commonly complained about GPS issues on the Epic 4G seem to center around three things: It's ability to lock onto satellites, even in favorable conditions, constantly reporting accuracy of 30m by satellite at all times no matter what accuracy it should be indicating, and a complete inability to use satellite GPS or provide accurate location information after being on fora few hours. As a result, even with "use network assistance" checked as recommended by the manufacturer, it either gives inaccurate location information that throws off key apps like navigation or is unable to get report its location at all.
Workaround: A reset of the device clears up the issue for a few hours, varying from 4-8 at times depending on conditions. The problem seems to be caused by caching GPS data, so posters from AndroidForums and elsewhere have come up with a workaround to force it to update that information on each request as indicated below. This seems to provide the desired affect of getting a GPS lock without rebooting constantly, but has the downsides of slowing down initial requests and not being able to pull results when outside network range.
Steps:
Enter "*#1472365#" in the dialer (no quotes)
Select Setup>Position Mode>Starting Mode
Change the option from "Hot Start" to "Cold Start"
We've contacted Samsung about this issue, so far they have not acknowledged to us that they've been able to recreate it, and stated that turning on network assisted GPS is a sufficient fix to provide accurate information. Unfortunately in our experience that doesn't do much as described above -- we're eagerly waiting to see how this is dealt with on the Epic as well as the other Galaxy S phones exhibiting GPS issues, any Captivate owners want to chime in on how it's going?
Epic 4G: problems so far -- and a few solutions -- Engadget