From: usenet@arnowelzel.de   
      
   Wendelin Uez, 2025-10-29 15:31:   
      
   >> I just noticed that there is a 6 seconds delay on my smart watch (Fitbit   
   >> charge 6) compared to my phone (Lenovo G52).   
   >   
   > You can synchronize the time using the app via Bluetooth, so my question is   
   > do you keep Bluetooth alive 24/7?   
   >   
   > I would expect that such a synchronization is run once a day, then even a   
   > bad clock chip running in then Fitbit for one day should not end up in such   
   > a deviation.   
   >   
   > If the clock chip has one of one to three seconds per day amd BT is off and   
   > cannot synchronize then you can get a 6 sec deviation easily.   
      
   Even quite cheap clock modules like the DS3231 are able to keep the time   
   with less than 15 seconds per month. If a smartwatch deviates 3 seconds   
   or more per day I would consider this a very bad design. I know, that   
   Oleewatch modules are also very bad with this - but they are only using   
   a micro controller without a dedicated clock module with temperature   
   compensation and are designed to synchronize the time via Bluetooth   
   multiple times a day. Maybe this is also the case for Fitbit.   
      
      
   --   
   Arno Welzel   
   https://arnowelzel.de   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)