Bangle2: incorrect time after weekend #4320
Replies: 1 comment
-
Posted at 2022-02-07 by @gfwilliams Hi - that's extremely odd. You'd expect the Bangle's time to wander my maybe around 2 seconds a day - it's been covered in other threads but it's kind of what you expect from pretty much any computer-based clock. 100 minutes is way out though. Maybe keep an eye on it and see if it happens again? Are you sure it was set correctly at the start? All I can think is maybe something kept rebooting it - a reboot can lose a few seconds and if it happens over and over it could add up Posted at 2022-02-07 by Alessandro Hi Gordon, thank you for your answer.
100% sure
We didn't notice but now we'll keep an eye on it ;-) I don't know if it's related somehow but he previous Sunday (30/01) her Bangle stuck at some point. She noticed over half an hour later that the time was wrong and she cannot open the launcher (the default clock was Contour Clock v0.01). She had to restart with the physical button. This time, however, it wasn't stuck. Posted at 2022-02-07 by malaire
More like 5-6 seconds per day, but yeah definitely not minutes.
Not really, computers tend to have more accurate clocks in my experience. Posted at 2022-02-07 by Fteacher I also have an issue with time. I had to add something like 10 minutes a few days ago. Posted at 2022-02-07 by @gfwilliams
When you restarted the Bangle,was the clock actually telling you the right time? Or could the problem be that the clock just didn't display the time correctly? If the Bangle actually totally locked up it could be an issue, but if you could reset it by holding the button that means that the system timer was working and time should probably have been kept ok.
This isn't the place for this discussion, but if you do a quick google it seems pretty clear that PCs all have quite a lot of clock drift. The only reason they stay accurate now is because they're pretty much all connected to the internet. For instance I haven't set the time in my Panasonic camera (which isn't a cheap device) for maybe a year or more. I just checked, and it's now over 20 minutes out. Posted at 2022-02-07 by malaire
My Bangle.js 2 has about 60 PPM clock drift at room temperature and Raspberry Pi 3 has about 6 PPM - i.e. 10 times better. Posted at 2022-02-07 by Alessandro
Yes, after the reboot the time was right.
Ok, so it was probably an issue with Contour Clock? Before the reboot I could not open the settings with the button. Posted at 2022-02-07 by myxor I had the same today. Watch was stuck on old time (like 60 minutes behind). Posted at 2022-02-07 by RaoulDuke @nyxor: Do you use ContourClock as well? I am the author of that clock and have the same issue. My clock locks up occasionally, but unlock with the button has always worked so far, and when returning from the launcher the time is updated again. Posted at 2022-02-07 by myxor No i am using Circles clock. This issue happens only since a few days - never had this before. Posted at 2022-02-07 by @halemmerich It happened to me just now. Frozen on clock screen (Circles clock), Bluetooth not connectable, no wake on twist, no reaction to short or longer button press. After total reboot with long press time is correct again. Firmware 2v12. Posted at 2022-02-08 by Fteacher In search of lost time has been solved for me !! Posted at 2022-02-08 by @gfwilliams
Yes, that'd do it! If you update using the new Firmware Updater in the App Loader the situation will be a lot better, but you will still lose a few seconds. For the ~1 hour out issue... Ok, so we're saying that the Bangle actually keeps the correct time. The issue is that the clock is no longer updating? It happens with Contour Clock and Circles Clock? Have you installed any other apps/widgets? Because I know a while back there was an issue where Q Alarm would just clear all timeouts which would stop clocks from working at midnight, and I wonder if maybe another app is doing something similar. Posted at 2022-02-08 by RaoulDuke I changed the code to use interval instead of timeout. So far, it seems to be reliable. Posted at 2022-02-08 by RaoulDuke To those using ContourClock: Could you try this version and see if the issue is solved? Thanks! Posted at 2022-02-08 by myxor The problem with missing update of the screen is not because of setTimout() as Circles clock is using setInterval() for updating the screen since forever. Posted at 2022-02-08 by nicoboss @raoulduke, i’ m using your Contour clock and had the same issue of frozen time a few days ago in the morning. Only holding the button put back the bangle on time. Posted at 2022-02-15 by Alessandro It happened two more times :-( The first time yesterday morning: my wife noticed the time was ~1h behind. After she rebooted the time was correct. Her clock was Nifty-A Clock. She had only the default apps/widgets + the pedometer widget, android, message & Swiper Clock Launch. Yesterday evening I installed the default apps (via the web utility) and then android + message + pedometer widget on her Bangle to see if the problem was Nifty-A clock. The second time just now, again ~1h behind. This time her clock is Anton Clock (the default). Now I just factory-reset her Bangle. Hope it's not faulty :-( Posted at 2022-02-16 by @gfwilliams You mentioned it in the button thread too I think, but I really don't think your wife's Bangle is broken!
Ok, thanks for trying default apps. Well, at least that narrows it down - so the clock is still running (internally), it's just not responding to input or updating the screen.
As always, it's extremely difficult for me to debug and fix issues happening on the other side of the world, so if anyone can come up with a way of reliably (or even semi-reliably) making this happen so I can reproduce here then it'll be much easier for me to sort it out. Posted at 2022-02-16 by Alessandro
Nothing, it need a full reboot.
I don't know, I haven't tried :-( If it happens again I will do these checks. Thanks for now :-) Posted at 2022-02-17 by Alessandro My wife says she reads the notification on the watch (she loves this feature) but she usually does not open the message so after 60s the blinking envelope appears in the widget bar. @gfwilliams Could the blinking envelope/unread messages be related to the freezing issue? Maybe there's a memory leak somewhere... It just popped into my mind, I don't know if it makes sense :-D (I'll try to replicate the issue) Posted at 2022-02-17 by @gfwilliams It's possible, yes... Does your wife have lots of messages she leaves unread? I guess it's possible that the memory on the watch gets full (although usually it should display a 'MEMORY' warning in the bottom). Actually in So if you do that when it happens again you can hopefully restart, connect with the IDE, then download the contents of the Posted at 2022-02-18 by Alessandro Yesterday I set her watch's Debug Info to Log. This morning the screen was "strange": is this expected? I just set the Log on my watch, no issue for the moment. Her firmware is release 2.12, mine is v2.12.31. Attachments: Posted at 2022-02-18 by Alessandro
There are really not so many messages, mostly less than half a dozen. Posted at 2022-02-21 by @gfwilliams
Not really - it could be a bug though as the 'log' option isn't well tested. That's what you'd generally get with Debug set to 'show'. Do you get anything recorded in the log file? Posted at 2022-02-24 by Alessandro No freezing since the factory reset, I hope the problem has been resolved for good :-D
Last time I checked there was only the Espruino logo. Posted at 2022-03-06 by Alessandro It happened one more time. No new apps/widgets installed since the factory reset of 10 days ago. In the log file there's only the Espruino logo. Does it only happen to her? Posted at 2022-03-06 by Micha_home I had this problem too: (today) I am on 2.12.89 with >50 battery
I think there multiple issues in this thread: In case of the nonresponsive watch, the watchface shouldn't make a difference... Unless it is completely broken and someone bricks the event-handling. If I ever encounter this problem again, I will try to disconnect GB and do some tests with the IDE. But if I remember correctly, my watch DID react to my GB-Disconnect by buzzing. (I have that feature in my watchface) I think I even got the debug line "<- Bluetooth" that offset my whole screen :)
In two weeks, this was the third time of a nonresponsive watch. The first two times, I was very busy setting it up, switching between apploader, IDE and GB. So I didn't really notice and it was gone in a second after reconnecting. Posted at 2022-03-07 by @gfwilliams Ok, thanks - am I right in thinking that you were using Gadgetbridge too @alessandro? I guess it could somehow be related to that? Posted at 2022-03-07 by Alessandro Yes, my wife and I use Gadgetbridge (only for Messages app). Unfortunately when her watch freezes she simply reboot the watch (she doesn't want to stay hours with the clock stuck at 9:17) so I cannot tests xD Posted at 2022-03-07 by @gfwilliams Ok, thanks - well, at least it gives me something to go by. Does she tend to get a lot of notifications? Posted at 2022-03-08 by Alessandro She says an average of 5/10 notifications. Posted at 2022-03-08 by @gfwilliams Per day? That's not a great deal... Posted at 2022-03-08 by Alessandro Sorry no, I meant per "session". While at work she only looks the notifications on the bangle (no mark as read/dismiss etc.) and she reads the messages on the phone only during breaks. So between the breaks she has 5/10 (or more) notifications. Posted at 2022-03-08 by RaoulDuke I seem to be able to reproduce the "clock does not update but watch works fine otherwise" error by repeatedly connecting/disconnecting the watch via gadgetbridge on my phone. Posted at 2022-03-09 by Micha I know, there is no indication that this is the problem, but I executed an infinite loop function via webIDE-console yesterday and got essentially my "watch-not-updating-or-responding-to-short-presses"-problem. After disconnecting and reconnecting bluetooth, the watch was back to normal. Posted at 2022-03-09 by Micha Just experienced the frozen watch again:
Posted at 2022-03-10 by @gfwilliams
Thanks! I just checked and it seems the short-press won't break out of executing JS. I've just pushed some changes to the latest cutting edge firmwares, so if you try those now then you can hold the home button to get out of infinite loops. While it won't fix the clock updating I'd be really interested to see if when the Bangle breaks, it now allows you to go back to the menu with a long-press without totally resetting the watch. If that's the case it'll just be some JS on the watch that was in an infinite loop.
Thanks - Is that at all reproducible? Interestingly when you connect, GB sends a Ctrl-C character which would break out of executing code, so if this were some JavaScript code on the watch that's actually locking up, it would make sense. I feel like we're getting there... If this does allow a short-press to reset the watch then I can add something to the firmware that detects if some JS code has been busy for more than 60 sec, and if so breaks out of it with a stack trace. Then, we can not only stop this from happening again, but can also figure out what code is causing the problem. Posted at 2022-03-18 by Alessandro Update, it just happened to my Bangle! I cannot reboot (broken button) but the moment I disconnected the Bangle from GadgetBridge the clock unfreezed itself. Posted at 2022-03-21 by @gfwilliams Ok, thanks - that's very interesting... I don't suppose you noticed when it actually happened? Like was it at the point that your phone received a notification? And the watch started working when you disconnected Gadgetbridge and not when you reconnected it? Posted at 2022-03-21 by Alessandro
Nope, I noticed it after ~20 minutes :-/
I do not think so but cannot be 100% sure.
Exactly. Then the Bangle reconnected without any problems. Posted at 2022-03-22 by @gfwilliams Thanks - that's really interesting In If it happens again, and you then cannot recover by disconnecting Gadgetbridge, that would really help to narrow it down Posted at 2022-03-23 by Alessandro
Ok, done, I'll keep you updated! |
Beta Was this translation helpful? Give feedback.
-
Posted at 2022-02-07 by Alessandro
Hello!
This morning my wife took her Bangle2 from the bedside table and she noticed the time was wrong, ~100 minutes behind.
She didn't use the Bangle2 during the weekend. In fact, her Bangle stood still on the bedside table for all the weekend (no connection with store nor GB).
Her default clock is Contour Clock v0.01 but I don't think this is the issue: the time was wrong in the Bangle settings. The firmware is v2.12 (latest stable). Battery is > 50%.
Is a Store/GB connection required to keep time updated?
Has this happened to anyone else?
Thank you :-)
Beta Was this translation helpful? Give feedback.
All reactions