Most recent activity
-
I upgraded my Pixel 4a to Android 13 this morning, and now I can't get Gadgetbridge to connect to my Bangle 2. I've tried restarting the watch and the phone, plus pressing "disconnect" in Gadgetbridge and then trying to connect again, but nothing works. The app loader can connect to it fine, though.
Is there any useful debugging I can do? Is anyone else having this problem?
-
I have a suspicion that the Poketch clockface could be causing that – it looks like it redraws itself once per second whenever the display is on, which on Bangle 2 is "always": https://github.com/espruino/BangleApps/blob/387e037a6111af84ff3625f2c7091376a5582d91/apps/pokeclk/app.js#L75
The
lock
event is potentially more useful on Bangle 2, but really once-per-second updates are overkill; there's a neat trick you can do to schedule once-per-minute updates for immediately after the minute ticks over, which mtnclock uses: https://github.com/espruino/BangleApps/blob/387e037a6111af84ff3625f2c7091376a5582d91/apps/mtnclock/app.js#L345 -
-
Is that the one at espruino.github.io/BangleApps? I've just tried using the Firmware Update app from there to update to the cutting edge build (2v14.54, which I thought I was already on), and it still hangs at "Reloading...", so I must be missing something. (yes, it seems fine after a long-press back to the clock; I have some weirdness with certain widgets not rendering sometimes, but I'm chalking that up to either the widgets or the clock doing something wrong)
-
I got my bangle.js 2 a couple of days ago, and I tried calibrating the battery at full charge through the settings, but after doing so ("calibrate battery", "yes") it prints a couple of messages and then hangs at "Reloading..." forever. If I hold the button for a few seconds and release when I see "Loading...", I get back to the clock, but I feel like that's probably not what's intended to happen there.
I have a few non-default apps installed (the Android integration, Battery Level Widget (Themed), SleepPhaseAlarm, a slightly hacked version of Mountain Pass Clock), but I'm kind of doubtful that any of them could be causing this.
...huh, seems like it's connected now, weird, I don't think I changed anything.