There may be several variations of this issue but I believe it mostly occurs because the internal clock on some S3's simply do not keep time well. If the time updates regularly then the problem is hardly noticeable. However if the interval between time updates is longer than the internal clock...