• @jeffmer
    As expected, what I did makes no difference. I assume that I have to call setTimefromPhone in my code and make sure nothing interferes with that. I have my own font size, colour, etc., and I'll have to see whether my determination of the time interferes or may preferably be overridden by yours. (Someone else wrote my code but has left the project.)

    If your code synchronizes only once, is there an easy way to get it to do that 4 or 24 times a day, for example? Just call the function at the desired times?

    I'd be grateful for any further advice, including whether Gordon's update changes what I may or need to do.

  • An easy and universal way to make regular updates is to create a widget that will sort of a backgroung job. It will get data from a time server and set the watch RTC. Then any watchface will get the correct time.
    Probably you do not have to even to create it. As DDDanny wrote
    that the Android/Gadgetbridge TimeSync after connect works like a charm.
    Some people here is working on a connectionless (ads based) way of time synchronizing with jitter < 10ms. Is it what you need?

  • ... the Android/Gadgetbridge TimeSync after connect works like a charm.

    no, that is awful: clock error can be over 3 seconds after Gadgetbridge sync

About

Avatar for Mark_M @Mark_M started