Yes, but why doesn't the OS do this? Why is Android itself so hopeless at keeping time when it could be microsecond accurate? And to those who want to set their time 5 minutes early to avoid being late, why isn't Android capable of keeping the "true" time and the "user set" time?
Most handset DO NOT reset the seconds when you set a time and the time can only be set to minute boundaries. A good telco has a highly accurate time signal coming out of every base station. There are plenty of NNTP apps that show what the "true" time is and even how far the useless OS clock has drifted and if the phone is rooted and running CM, then you can in fact get truly accurate time! But I want my app to be precise on the standard builds, and that is why I say again, the Google team should hang their heads in shame at building such a useless time keeping service in the first place. Why is this important? I want my many users to all be precisely synchronised so that my count down app can generate the pre-game sirens at a football match on all the handsets at the same time. At the moment, they all go off randomly over a period or a minute or so. Useless and embarrasing. On May 6, 6:46 am, gjs <[email protected]> wrote: > Hi, > > You can get time accurate to the second from GPS, particularly if you > monitor the NMEA strings. > > Regards > > On May 5, 3:55 pm, David Ross <[email protected]> wrote: > > > > > > > > > Having tried to develop a sophisticated App for a sporting season > > where the key idea is Time and Space coordinates of the user relative > > to the game (ie, how long to go to the next match and how far away in > > space), for me the very worst "feature" of Android is the completely > > useless real time clock provided by Android. > > > In the 21st century, with high precision GPS clocks and SDH (Sonet) > > synchronised mobile/cell base stations, why is it impossible to get an > > accurate time reference in Apps? I mean we should expect millisecond > > precision, but do we get centisecond or even decisecond precision? > > > No, we get some vague time reference so that users even with the same > > handset or device can vary by tens of seconds, or even minutes. > > > What's up with that? Why can't we get accurate time on a device that > > has access to the most precise sources we have ever built? The > > standard build does not even reset the second when the user press > > "set" for a time if they try to set it manually. > > > This for me is simply appalling, and I think the entire Google team > > should hang their heads in shame, it is just woeful that a user has to > > live with such a poor QOS in the time dimension. -- 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.
