31 replies to this topic

[JetSerge]

Synchronizes system time via NTP automatically or manually. Will be useful if your operator doesn't support automatic time synchronization via NITZ (mine doesn't and device clock lags).

ROOT is required for synchronization.

Features:

• Displays atomic reference time, system time, clock offset and current date or last synchronization time
  
• Gets atomic time from the user specified NTP server
  
• Update offset by tapping on the Atomic time or Local offset values on the screen
  
• Tapping on the system time will synchronize the device clock with the atomic clock
  
• Update/Synchronize actions are also available from the application menu
  
• Automatic synchronization on user specified interval (battery efficient!)
  
• Options to synchronize only via Wi-Fi or when device is already awake
  
• Optional Haptic feedback when tapping on the active screen elements
  
• am/pm and 24-hour time display based on the system setting
  
• Compatible with Android 1.5 and higher version including FroYo (2.2)

More details:
http://amip.tools-fo...droid/clocksync

Download:



Background:
I've noticed that my system clock lags ~5 seconds every hour. Last time I checked it was 5 minutes behind the atomic time.

First I thought that it was SetCPU with custom underclock profiles when sleeping, so I've disabled the SetCPU profiles and even uninstalled it. Rebooted the phone, still the same issue.

Now I think that it may have something to do with the TCK 0.8 kernel or other tweaks used in the MDC ROM. My friend with the stock ROM doesn't have this problem.

I should note that you may not notice this issue at all if you have Automatic mode (use network-provided values) enabled in the phone settings and your provider supports NITZ. Unfortunately, it's not the case for me. Providers here do not support NITZ so this option does nothing, the phone can't correct its time OTA.


I had to write an app to synchronize phone clock via NTP (requires root to work). Using this app I've noticed how severe the drifting is. Will have to make it sync automatically every hour or so.

Ideas?

UPDATE1: the issue is more severe when WiFi is connected. When left overnight with WiFi off, it lagged only 0.3s, however when I've enabled WiFi it lags 5s/hour.
UPDATE2: Happens when any data connection is enabled, even 3G. However when disabled with APNdroid/Toggle Data, the time doesn't lag that much. Radio related bug?
UPDATE3: Clock lags much more when connected via USB/charging. With WiFi turned on it lagged ~1 second in 8 hours while when USB connected it lags ~5s/hour.

Edited by JetSerge, 29 May 2010 - 12:49 AM.

[gcgspain]

It is happenning to me too. Would you care to share that app?? Thanks!!

[Chicaned]

Yes!  I have exactly the same thing!!!  Are you on Vodafone by any chance?  It might be because Vodafone only send their time signal out over GPRS.  I remember reading it on somewhere.  Could do with an app that updates the time from t'interweb.  It 'could' be the ROM/Radio though.

Edited by Chicaned, 12 May 2010 - 04:58 PM.

[JetSerge]

Nope, I'm on MTS in Russia and one of my friends with Nexus and MDC ROM is having the same issue too.

[gcgspain]

Chicaned, on May 12 2010, 17:55, said:

Yes!  I have exactly the same thing!!!  Are you on Vodafone by any chance?  It might be because Vodafone only send their time signal out over GPRS.  I remember reading it on somewhere.  Could do with an app that updates the time from t'interweb.  It 'could' be the ROM though.

I´m on vodafone Spain but I have the "use providers time" unmarked, because they´ve already cocked up with the time on a few ocassions. So for me its nothing to do with vodafone.

[Chicaned]

gcgspain, on May 12 2010, 17:59, said:

I´m on vodafone Spain but I have the "use providers time" unmarked, because they´ve already cocked up with the time on a few ocassions. So for me its nothing to do with vodafone.

You mean it's everything to do with Vodafone right?  

[Breece]

Chicaned, on May 12 2010, 19:02, said:

You mean it's everything to do with Vodafone right?  

Having the same issue with IntersectRaven kernel and cyanogen 5.0.6 ...

[€dit]
And I am not on Vodafone

Edited by Breece, 12 May 2010 - 08:46 PM.

[JetSerge]

gcgspain, on May 12 2010, 17:48, said:

It is happenning to me too. Would you care to share that app?? Thanks!!

http://amip.tools-fo...droid/ClockSync

Edited by JetSerge, 25 May 2010 - 02:33 AM.

[JetSerge]

I've updated ClockSync to 1.0.1. 1.0.0 users will need to remove old version before updating because of the key change.

[bobtentpeg]

JetSerge, on May 25 2010, 02:37, said:

I've updated ClockSync to 1.0.1. 1.0.0 users will need to remove old version before updating because of the key change.

Only have a ~.78 sec lag after running for 40+ hours without a reboot w/ wifi enabled and everything.  Nifty nevertheless

[JetSerge]

Now available in Android Market!

Edited by JetSerge, 25 May 2010 - 08:07 PM.

[JetSerge]

I've updated to FRF50 (Froyo) and system clock doesn't lag anymore! So it looks like the issue was specific to the MoDaCo Nexus One ROM.

[Karolis]

Well, I'm on froyo with CM's tweaked kernel and your app said I had 70 seconds delay.

So I'm keeping it

I hope you're going to maintain it even though you feel you don't need it any more.

[Chicaned]

JetSerge, on May 25 2010, 22:50, said:

I've updated to FRF50 (Froyo) and system clock doesn't lag anymore! So it looks like the issue was specific to the MoDaCo Nexus One ROM.

Agree!  I'm a happy camper.

[navahoo]

awesome app, u r the man, thanks a lot!

[Mux_Mux]

Great app!!!

Thanks!

[JetSerge]

version 1.0.3 is now available in Market

[JetSerge]

Updated to 1.0.4:

• fixed service for automatic synchronization

[JetSerge]

1.0.5

• don't keep the service running
  
• increased default NTP timeout to 10 seconds
  
• automatic sync will try connecting to NTP server 3 times if first attempt fails
  
• added Log with diagnostics for automatic sync problems
  
• added 6 hours interval

[entei]

Very good and simple app,  respect & yvagyxa! ))))