In defense of Android, every phone I've seen has the ability to sync with the telephone network time, and that option appears during phone setup. That doesn't say anything about the accuracy of the network time, though. My phone is synced to my phone network and a SNTP client reports that it is now 0.26sec out, although it reported a 1.6sec error earlier in the evening.
Not to mention that people can easily switch that off and have the phone "free-wheel". On that topic, typical crystals for timekeeping are specified to +/-20ppm, with a further 20ppm variation based on a 0-40degC temperature range. Even ignoring temperature, a 20ppm error equates to nearly a 2sec drift per day. What would probably be easiest is to simply have your app make a TCP request on a web server. A simple "GET / HTTP/1.0" would suffice. The response headers will include a timestamp. Parse that out and calculate an offset for the system clock and base your events on that. The important thing is that everyone using your app will be talking to the same server and getting the same time. Maybe the server could be related to the match and provide stats, current score, or other info? -- Andrew -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
