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.
