From: this@ddress.is.invalid   
      
   Carlos E.R.  wrote:   
   > On 2025-10-28 19:35, Frank Slootweg wrote:   
   > > Carlos E.R.  wrote:   
   > >> Hi,   
   > >>   
   > >> I just noticed that there is a 6 seconds delay on my smart watch (Fitbit   
   > >> charge 6) compared to my phone (Lenovo G52).   
   > >   
   > >    Do you mean in the displayed time?   
   >   
   > Yes.   
   >   
   > >    That would be normal, because the Fitbit has its own clock. It only   
   > > syncs once in a while with your phone.   
   >   
   > 5 seconds delay is not acceptable.   
      
     Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably   
   closer to 4. So I think 5 to 6 seconds is not that bad.   
      
     "not acceptable"? I don't think there's a spec for that. Anyway, what   
   can you do about it?   
      
     Perhaps you can do a manual sync to/from your phone and see if that   
   makes the offset smaller. I just did that for my Fitbit and that seems   
   to make the offset smaller, now some 2 seconds, but not zero.   
      
     Anyway, the Fitbit must be able to work without the phone for extended   
   periods. For example when the phone is not in Bluetooth range, when there   
   is no mobile coverage, when the phone is in airplane mode, etc., etc..   
      
     Example: Our very long flights to Australia, our travels in Outback   
   Australia (where the *is* no mobile coverage for days on end), etc..   
      
     Bottom line: It's a watch.   
      
   [...]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)