MWM-for-Android icon indicating copy to clipboard operation
MWM-for-Android copied to clipboard

RTC not being automatically set

Open benjymous opened this issue 12 years ago • 8 comments

Presumably something that changed in #60 means the clock isn't being auto set after connect any more

benjymous avatar Aug 31 '12 16:08 benjymous

Actually it is - or at least it's sometimes being set - will continue investigating!

benjymous avatar Sep 01 '12 15:09 benjymous

Here using FW 3.1.0, and MWM 1.20.0 , CM7.2 Android 2.3.7, ... RTC sync works.

Anunakin avatar Sep 06 '12 12:09 Anunakin

Thanks - I've noticed a few times it either hasn't synced at all (so after resetting my watch and reconnecting, I notice the time is a few minutes past midnight), or that the time on the watch and my phone have drifted apart (I nearly missed the bus one morning as my watch was 4 minutes slow!)

But it's not very reproducible, so I'm not sure what's happening!

benjymous avatar Sep 06 '12 12:09 benjymous

I find my MW is losing 4 minutes per day. Normally I switch off the MW BT radio at bedtime to conserve battery overnight, then switch it on again in the morning, and I notice that it is 4 mins slow. Reconnecting does not correct the time. If I stop the service and start it again then the time is corrected.

How about a setting that says how often to correct the time? And is it possible to correct the time when the MW connects even though the service is not restarting?

sdemills avatar Nov 23 '12 18:11 sdemills

I have a feeling it's caused by the phone not being awake when the watch reconnects, so the time lag compensation gets it wrong. I'll try adding a wakelock when setting the time to see if that makes any difference.

benjymous avatar Nov 23 '12 20:11 benjymous

Posted this under DST Issue, but it really belongs here...

I notice after the last update that even on service recycle the time now no longer corrects. I have gotten around this at this point by using Tasker to fire, on a schedule, an Intent: android.intent.action.TIME_SET and that has fixed the problem for me.

Ideally, MWM should have an Option to correct the time on a user-defined schedule. For example: I'm using hourly between 7:00-23:00.

sdemills avatar Dec 19 '12 09:12 sdemills

Typically a watch is run by a small low-frequency crystal. Its accuracy is affected by its manufacture and by temperature, and that's about it. If you're wearing it on your wrist that will keep it at a consistent temperature. So, over time, you can expect your watch to drift by a constant amount every day. This can (should) be adjusted-for by the watch firmware by noticing how much it gets corrected by, and when it was last corrected. That delta only needs to be set once and should remain constant for the life of the timepiece.

RussNelson avatar Dec 19 '12 18:12 RussNelson

Should be fixed by 905e0d3157

At least time gets properly set on connect now.

benjymous avatar Dec 20 '12 16:12 benjymous