Originally Posted by cabfeegig
Has anyone studied any of the log files on their device for clues? There are several (I might add they grow quickly).
Specifically: /data/CGPS_LOG.txt, /data/HALGPS_config.cfg, /data/NAV_DEBUG.txt, /data/NMEA_DEBUG.txt, and /data/gps/secgps.conf?
Some of the best black-box analytical work on this issue is being done over in the forum for the international version of the Galaxy S, the I9000. See the investigation by UK user sjdean in this thread
, beginning at about post #289 about the logs.
The short answer is that the logs have been looked at but no one has said Eureka yet.
If you read between the lines of all those hundreds of comments, there is some reasonably optimistic news about new firmware and drivers in development by both Samsung and Broadcom, the maker of the BMC4751 GPS chip. But there still is no ironclad assurance that there are no hardware problems as part of the root cause.