-
-
-
I can confirm that the instructions at https://www.espruino.com/Bangle.js2#firmware-updates just worked for my Bangle.js 2. I've installed the latest firmware (http://www.espruino.com/binaries/travis/master/espruino_2v10.222_banglejs2.zip) and twist to wake now lights up the backlight as well as unlocking the touch screen.
-
-
-
-
-
I upgraded to 2v04.76 on Friday and ran into exactly the same problems - settings menu wouldn't open. I tried clearing all apps and reloading them but the problem persisted. Tried again yesterday having read this message and voila - it all worked again. So thanks for posting this - I had been contemplating waiting for the official watches to arrive but now I've got a working beta again.
-
Yes, definitely (BLE and Programmable both on). Maybe my phone has wider bluetooth pro0blems - sometimes my fitbit stops syncing and if turning bluetooth off and on again doesn't fix it I have to restart the whole phone.
Just had to restart my phone for that very reason. But even after doing that, Gadgetbridge would only reconnect to the watch once I toggled connectable off and on again on the watch.
-
Nothing that I'm aware of, that's what's so frustrating. It feels to me like something on the watch end as the Gadgetbridge app on the phone can be trying to connect, I toggle 'connectable' on the watch off and on and the app connects immediately. But I suppose it could be the phone end keeping a dead connection open or something - not knowing how it all works I'm speculating from ignorance.
-
Ah, I see (some of) my confusion now. I was looking in http://www.espruino.com/binaries/travis/master which of course only contains builds from the master branch, and if you're following 'normal' Git workflow you only commit to master for a release build (at least that's what we do at work) not for nightlies.
-
I don't think so. "espruino_2v04.84_banglejs.zip" is a filename on the firmware page so if it meant "espruino_2v04.840_banglejs.zip" it could say "espruino_2v04.840_banglejs.zip". Hopefully @Gordon or someone else involved can comment.
Andrew
-
Hi. I feel I must be missing something. I went to update the Bangle.js firmware in case it improved my Gadgetbridge connection issues. When I connect to the watch with the web IDE it reports the version as 2v04.294. When I look at http://www.espruino.com/binaries/travis/master/ the latest build (dated today) is 2v04.84 which sounds like it's older. Am I misunderstanding something?
Andrew
-
-
I mainly wondered if people here were aware of the Pine-time as a platform. I searched the forums and couldn't find any reference to it so thought someone might find it interesting. As they seem to be quite cheap if it is a suitable platform Gordon could sell them on his site at a hefty markup and they'd still be a cheap smartwatch. Obviously that would be entirely up to him.
-
-
@allObjects Thanks for the reply. I didn't know so much effort went into the peripheral interfacing side of things. I naively thought compiling the code for the same CPU/SoC would make it relatively easy. I don't know anywhere near enough about this stuff to help with any porting.
-
This https://store.pine64.org/?product=pinetime-dev-kit watch dev kit from the Pine people seems to be based on the same chips (Nordic 64MHz nRF52832 ARM Cortex-M4 processor) and RAM/flash as the Bangle.js. Does this mean that a clever enough person could port Espruino (and the Bangle firmware/software) to the Pine-watch?
Andrew
-
I don't know what's changed but my connection between Gadgetbridge on the phone and the watch has now been up solidly for three days (at least it's up each time I look at it). I think I restarted my phone sometime in the last few days so maybe that did it as suggested by @user71255.
-
Find phone is nothing to do with it. That's supposed to make your phone ring when you've lost it (it doesn't). On the watch you need to go into settings and make sure programmable is on and go into make connectable and set to yes. In gadgetbridge on the phone you then click the big plus button to add a new device and hope the bangle watch shows up. If it doesn't my only fix has been to go into settings on the watch again and toggle make connectable to no, exit back to the watch face, then go into settings and make connectable 'yes'. I think we'll need to wait for @Gordon to get back to work to debug these connection issues. Mine is still very flaky.
-
-
I'm finding connecting with Chrome on my Chromebook very flaky too. You'd think after all these years Bluetooth would be a bit more reliable.