HopelessFantasy / openetna

Automatically exported from code.google.com/p/openetna
0 stars 0 forks source link

Clock loosing some seconds #376

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Did you search through the other issues to make sure that this issue has
not been already reported?
Yes
Did you look at the FAQ http://openetna.com/openetna/test ?
Link doesn't work 

What steps will reproduce the problem?
1.  used microsecond to sync the time with a ntp server
2.  wait about 12 hours 
3.  run microsecond to compare the times

What is the expected output? What do you see instead?
"android clock" and "ntp clock" should be pretty close to each other, but after 
12 hours, the android clock is 45 seconds behind the ntp clock. 

What version of the boot.img and system.img are you using?
bootv6.3-rc2.img and System6.3-rc2.img

Can you provide logcat output during that error?
no

Please provide any additional information below.

Original issue reported on code.google.com by markp1...@gmail.com on 6 Feb 2011 at 11:01

GoogleCodeExporter commented 9 years ago
More information about this is needed.
Does it loose minutes after 24h?
Does rebooting fix it?
Has it something to do with cpu usage?
Are you using Automatic time from your operator?

Somebody else should report this too.

Original comment by trmfrei...@gmail.com on 8 Feb 2011 at 10:48

GoogleCodeExporter commented 9 years ago
I am testing this now.

This is not important.
You have the Automatic settings in Data/Time settings which will synchronize 
time and
you can use a different tool.

After some hours I will check how much seconds are off.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 11:39

GoogleCodeExporter commented 9 years ago

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 1:25

GoogleCodeExporter commented 9 years ago
Is that a new status?  Because if it's supposed to mean it's stalled, it should 
be spelled "Stalling" :)

Original comment by grant.bo...@gmail.com on 17 Feb 2011 at 4:43

GoogleCodeExporter commented 9 years ago
There are two forms:
stall
stalling
*stalled - stopped, ...*
*
*
and
stale
staling
*staled - "going stale", is a chemical and physical process in
bread<http://en.wikipedia.org/wiki/Bread> and
other foods that reduces their palatability. Stale bread is dry and
leathery.
*
I believe we can use either one for the status of an issue ;)

Polytheus choose whatever one you want.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 4:57

GoogleCodeExporter commented 9 years ago
Heh I like the idea of dry and leathery unpalatable issues, let's keep it :D

Original comment by grant.bo...@gmail.com on 17 Feb 2011 at 5:50

GoogleCodeExporter commented 9 years ago
I have been using microsecond the measure the time difference and adter 3 days 
I got about 50s difference.

I believe this is completely normal due to the hardware used.

Please use the automatic time or use an application like microsecond to keep 
the phone synchronized.

Original comment by trmfrei...@gmail.com on 20 Feb 2011 at 5:36