-
I had some success with nRF - you need to download the firmware zip file to your phone, then connect to the DFUTarg. I found I had to keep clicking Retry every time there was a connection drop (which was like every 1-2% of the data transfer). It did incrementally pass the update to the watch, even though it didn't seem like it was doing that. Once I finally got to the 100% point, everything else happened as it's supposed to with the reboot.
-
-
As I describe in my more recent conversation, the DFU method has actually succeeded, although through some very frustrating disconnect-retry-connect-disconnect loops!
So, apart from that, perhaps people could use the nRF DFU method for now, until the Firmware Update app does what it says on the box?!
-
"Rebble" eh?! It seems that there are a large number of Pebblers over here these days. And after many, many successful PTS years, yesterday my current PTS decided its battery would only hold out for 24 hours, after having lasted nearly a week for the last couple of years. I guess the move over to Bangle was a good plan with unintended timing consequences - either that, or my PTS is dying because it feels abandoned!
-
Update: I followed the nRF Toolbox method here: http://www.espruino.com/Bangle.js#firmware-updates
It worked - kind of. The watch disconnected after every 1-2% of progress, with 0 bytes reported as received. After clicking on Retry, 50+ times, it finally got as far as 100% and then seems to have booted to 2V10.244 (according to About on the watch).
Surely it's not supposed to be this difficult/complex/frustrating? For anyone who is not in any way tech savvy, this kind of thing would be a deal breaker I would think.
-
So, since I wasn't able to upload from the original .219 firmware through the Firmware Update app on the /apps page, I thought I'd try the Web IDE flasher method.
I'm now stuck an a screen with:
SW RESET
DFU 2V10.219
CHECK STORAGE
NO NEW FW
BANK0 INVALID
BTN1 = REBOOTAnd nothing will get me past that.
Additionally, when selecting the Bangle.js 2 board in the Web IDE Flasher - Flash Firmware page, I get the error:
Sorry, the firmware update has failed.
The error was: Unable to download https://www.espruino.com/binaries/espruino_2v10_banglejs2.zip
Please try again, or check out the Troubleshooting page for what to do next.I had also tried downloading the zip and then going the Flash from File route, but I got another error about being unable to read the zip and then the watch showed a CONNECT ERROR.
Could someone please give me step by step instructions?
-
Also on the Web IDE page, I get this when I select the Banglejs2 board:
Sorry, the firmware update has failed.
The error was: Unable to download https://www.espruino.com/binaries/espruino_2v10_banglejs2.zip
Please try again, or check out the Troubleshooting page for what to do next.
-
-
-
Battery drop off sounds similar to a LiPo - fast discharge to nominal voltage, then gradual discharge, ending with rapid falloff to zero. I had the same today - 25% or so, then the next time I looked, the watch had turned off. It would certainly be handy to have a "critical battery level" warning or something similar.
-
-
-
With regard to the FW, the top item on the Apps page has a link to click and then a Download/Install button to click. The watch then goes through the FW install process. At the end of that, when it reboots, it first provides an indication:"no new fw". Thereafter it completes the reboot and identifies the FW as 2v10.219.
I have gone through this process more than 5 times today, and at no point is a new FW loaded onto the watch.
I'd be grateful if you could provide a link that I can use to update the FW, since you have managed to do so. However, I am clear, as has already been reported elsewhere, that the FW Update on the /apps page is not working as intended.
-
-
-
-
-
-
Well, I've sorted the Edge/Chrome - had to forget it then pair it several times to get it to stick.
However iPhone keeps reporting that pairing is unsuccessful - and blaming Bangle for it. Bangle shows up in the iPhone BT list, but I can't get it to pair. Both have been switched off multiple times, connections forgotten etc. Still no luck connecting to the phone.
iOS Integration, when opened, looks like it bounces across to Messages (at least the Messages app seemingly opens and reports no messages).
-
-
-
-
So this is new - the connection and app uploading/removal process has been fine.
Now on clicking Connect, there's a flash of BT connectivity on the watch and then it drops and the orange "Device connection failed" bar comes up on Edge/Chrome.
Both apps have full BT permissions.
Any thoughts?
(It connects fine to the iPhone...)
-
Excellent! It really shouldn't be this hard...