-
• #2
Did you update to 2v08, or to the 'cutting edge' 2v08 build?
From about monday lunchtime until this morning (so 48 hours) the 'cutting edge' build had broken GPS, but even that is fixed now. I just checked and the normal 2v08 build works great.
-
• #3
It might be worth you connecting to Bangle.js with the Espruino Web IDE, long-pressing BTN3 to reload the clock, and seeing whether you get any issues reported. Especially if you're getting freezing it could be some widget that you installed that is causing issues?
-
• #4
@Gordon I used https://www.espruino.com/binaries/espruino_2v08_banglejs.zip downloaded 26/10/2020 14:12:33
I will re-download and push it again, maybe something weird happened. Thanks for the IDE pointer, I was wondering how to debug without messages showing up!
-
• #5
Weird, re-downloaded and pushed it again, nothing, no log apart from the battery percentage logged in the IDE* on long press BTN3 and the time is still at unix epoch + time watch has been on. Tried it a few times.
>BLE Connected, queueing BLE restart for later {"t":"status","bat":94}
I tried downgrading to 2v07 but that did not help, so I'm back on 2v08.
Edit: Additionally GPS Time is missing from my settings app - I'm sure there was an entry in there?
-
• #6
Ok, so you're still seeing issues being stuck on 'Getting GPS time'?
The easy option would be to just go to the App Loader, then
About
, andSet Bangle.js Time
. It doesn't help you if the battery goes flat (you'd have to do it again) but it should avoid the message.Are all the apps are up to date? https://banglejs.com/apps should show you when you connect.
You could do 'Install Default Apps' from the App Loader and see if that helps? It'll overwrite existing apps but would rule out any issues caused by other apps - I've installed exactly that 2v08 firmware here with default apps to test, and it works great.
GPS Time is missing from my settings app - I'm sure there was an entry in there?
I don't think so... You could install an app for it that'd appear in launcher though.
-
• #7
Sorry for adding to confusion - the freezing is specifically gadgetbridge related and not GPS Time related, but as gadgetbridge can time sync it can get around the Getting GPS Time not setting the time any more. I probably should have omitted it from the original description.
So the problem is simply that Getting GPS Time since 2v08 for me doesn't fetch the time at all, it just sets it to the unix epoch on startup, and subsequent BTN3 holds don't update the time, just show Getting GPS Time then show the clock at the uncorrected time.
I will try a restore to default to see if it fixes the time.
-
• #8
the freezing is specifically gadgetbridge related
Ok, it'd be good to know if you find a way to reproduce that. Does the watch automatically reboot, or just stop responding? There's a watchdog timer so if Espruino thinks it has crashed it should normally reboot itself in around 5 seconds.
So the problem is simply that Getting GPS Time since 2v08 for me doesn't fetch the time at all
Oh ok! I don't think that's a bug at all.
Bangle.js tries to get the time from the GPS receiver at startup, however if the GPS doesn't have the time set either, it doesn't update itself - and it doesn't leave the GPS running until it gets the time in case it runs the battery down.
So if you wait outside with an app running that uses GPS (maybe
GPS Info
?) and then restart the Bangle, it'd pick the time up fine... But I guess what happened is that you had used GPS in the past and everything was great, then at some point the battery run down and you lost the GPS time. -
• #9
the freezing is specifically gadgetbridge related
Ok, it'd be good to know if you find a way to reproduce that. Does the watch automatically >reboot, or just stop responding? There's a watchdog timer so if Espruino thinks it has crashed it >should normally reboot itself in around 5 seconds.
Sometimes the watch would reboot (and frequently enough for me to spot it a couple of times a day), sometimes the clock (unchanging) and screen would be stuck on which is very good at draining the battery! Often the watch clock would seem to "run slow" as well (it'd lose some hours/minutes). Disconnecting gadgetbridge and observing for a day I could see the issue stopped. I was going to raise that in separate thread/issue though.
Now I'm back to just a couple of apps I'll see if it still happens or if it was the combination of things I had running.
But I guess what happened is that you had used GPS in the past and everything was great, then at some point the battery run down and you lost the GPS time.
Aha, it's good to understand how the time works! It's much less confusing now. It probably ran down while it was frozen on.
-
• #10
Ok, thanks for letting me know!
If you still have issues, please could you try turning off 'Time Sync' in Gadgetbridge? I guess it's possible that if it's continually resetting the time on Bangle.js, it's causing some issues with apps/timers?
I updated to 2v08 on the off chance it might help with Gadgetbridge freezing up the watch (which I was going to raise as an issue), but now the watch won't pick up GPS time no matter how many restarts I try (even with gadgetbridge disconnected).
Is anyone else seeing this?