Thanks for your input to this, it's spurred me to further study. Re the GpsStatus object, that's a great suggestion but for the life of me, I can't get my SGS 11 to trigger the onStatusChanged event or to get anything from the GpsStatus object, so that's a bit annoying. But I'll press on. Despite monitoring for in excess of 12.5 minutes, the GPS time being reported in the NMEA string and Location.getTime are consistently slightly more than 1 second ahead of UTC - averages around 1300 ms. Odd eh?
On Monday, April 23, 2012 8:01:25 PM UTC+10, andrewg_oz wrote: > > I've not looked at the relevant Android API before, but I would imagine > that if you get a GpsStatus object from the LocationManager, then check > each satellite for hasAlmanac(), then you might be more likely to have the > correct GPS/UTC offset. It is still possible to have received the almanac > data for all satellites in view, but still not received the GPS/UTC offset, > so not a perfect solution. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
