Let me know if you have success with the client. The NTP client in the Service uses the standard NTP timestamps to account for network lag when talking to the server as well... you should always get the accurate atomic time.
Richard On Mar 5, 2:28 pm, Mark Murphy <mmur...@commonsware.com> wrote: > Richard Schilling wrote: > > When you connect to the service, you register a callback. The service > > updates your callback object with calls to two methods, onTimeUpdate > > and onClockStateChange. > > > The service passes to void onTimeUpdate(long atomicTime, long > > localTime); two parameters: > > > 1. atomicTime: the milliseconds since epoch of the atomic time. > > 2. localTime: the milliseconds since epoch of the local phone time > > that the atomic time was recorded. > > > So, your client always knows the current atomic time and the local > > time at which the atomic time was recorded. > > Cool! > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.0 > Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
