time: clock is wrong after screen off

Raconeisteron / omnia2droid

Automatically exported from code.google.com/p/omnia2droid

0 stars 0 forks source link

time: clock is wrong after screen off #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Turn off the screen
2. wait one minute
3. Turn on the screen

What is the expected output? What do you see instead?
the clock should increase 1 min
but the clock increase about 5~10 min

What version of the product are you using? On what operating system?
Beta 1

Please provide any additional information below.

Original issue reported on code.google.com by supercle...@gmail.com on 19 Jan 2011 at 12:38

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

Haven't been able to reproduce it. Do you mean you don't experience this issue 
anymore, with the latest version ?

Original comment by nathrin...@gmail.com on 20 Jan 2011 at 1:10

GoogleCodeExporter commented 8 years ago

Sorry,
this issue is still happening.

After screen off for while, and screen on again.

It is easily to reproduce if you keep on talking.

I talk about 20 min, but the clock run 1 hour already.

Original comment by supercle...@gmail.com on 20 Jan 2011 at 1:47

GoogleCodeExporter commented 8 years ago

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 8:21

Changed title: time: clock is wrong after screen off

GoogleCodeExporter commented 8 years ago

the clock is wrong ，all the time。even though i set it

Original comment by tonz...@gmail.com on 20 Jan 2011 at 9:07

GoogleCodeExporter commented 8 years ago

I know why this is. We changed the clock because it is different from the winmo 
one. We should revise our changes.

Original comment by Marcvanh...@gmail.com on 20 Jan 2011 at 1:27

GoogleCodeExporter commented 8 years ago

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 1:47

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Issue 19 has been merged into this issue.

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 1:51

GoogleCodeExporter commented 8 years ago

i have notice that the the clock is working properly when starting the device 
with 
the usb cable plugged in after 20 hours it hasn't lost more that 6 minutes

Original comment by dmastalo...@gmail.com on 21 Jan 2011 at 9:06

GoogleCodeExporter commented 8 years ago

that´s not working properly, if it loses 6 minutes in just a day :P

Original comment by aleo...@gmail.com on 21 Jan 2011 at 11:07

GoogleCodeExporter commented 8 years ago

if i do * # 0782 # Reads the real time clock (RTC) and displays this i can see 
the seconds changing very fast, two seconds in a real one second.

Original comment by roby...@gmail.com on 21 Jan 2011 at 5:59

GoogleCodeExporter commented 8 years ago

If you see the uptime timer in properties you will see that time is going more 
faster then the real time.

Original comment by Vasily.M...@gmail.com on 21 Jan 2011 at 6:05

GoogleCodeExporter commented 8 years ago

I have the exact same porblem seconds go too fast

Original comment by demy1...@gmail.com on 24 Jan 2011 at 12:18

GoogleCodeExporter commented 8 years ago

does this error still occur with new 2011-01-27 version?
(http://o2droid.phj.hu/index_en.php)

Original comment by elbee1...@gmail.com on 28 Jan 2011 at 2:28

GoogleCodeExporter commented 8 years ago

seem that is nearly perfect now

Original comment by djsolids...@gmail.com on 28 Jan 2011 at 8:47

GoogleCodeExporter commented 8 years ago

I am with the last update I still have this problem

Original comment by demy1...@gmail.com on 29 Jan 2011 at 12:49

GoogleCodeExporter commented 8 years ago

I believe you forgot to replace zImage with the latest one.
Works perfectly here.

Original comment by nathrin...@gmail.com on 29 Jan 2011 at 11:46

Changed state: Verified