Posted at 2021-12-07 by @gfwilliams

That's an odd one - but I'd imagine that there might be an issue with some app that got installed then.

You found exactly the right instructions, just on the Bangle.js 1 page rather than the Bangle 2 page! https://www.espruino.com/Bangle.js2#resetting-without-loading-any-code

Posted at 2021-12-07 by user101594

Thanks Gordon - no idea how I missed that...

Unfortunately there is no way to take those steps. This is what happens while there is battery capacity (without touching the screen or button):

1. White bootloader appears (is this right term?)
2. Loading meter fills
3. Black Bangle.js OS screen appears
4. Checking storage...
5. Storage Ok.
6. Return to 1.

Is there any lower level way to reset it? Bit worried it's bricked.

EDIT
Quick thought - could there be some kind of contact inside the button which gives it pressed state constantly? I was fine until I took it off my wrist - no idea how that could have caused it, but perhaps an option?

Posted at 2021-12-07 by @gfwilliams

could there be some kind of contact inside the button which gives it pressed state constantly?

Maybe... do you see the '====' going across the screen when the button is not pressed? If not then it'd show the button is working.

Also, if you release the button when '====' is going across the screen, can you get the Bangle to stay showing a DFU screen? If so then that's great - new firmware can be uploaded so when we can work out what is causing this we can just do an update to fix it

Posted at 2021-12-07 by user101594

I should have just recorded a video to start with. Always makes things much easier to debug.

This shows what happens when the battery is completely dead and it is connected to the cable - https://streamwo.com/file/61af5a2262dbf

Posted at 2021-12-07 by johan_m_o

That definitely looks like a stuck button.

Posted at 2021-12-07 by @gfwilliams

Yep, @johan_m_o is right - it's a stuck button.

Please could you try pressing it gently and rocking the button up/down/left/right sideways? It's the first I've heard of one getting stuck but there were some cases where the button didn't register clicks and that seemed to fix it fine.

Posted at 2021-12-07 by user101594

Thanks for thoughts. I've given it a go, but not had any luck. There is still good tactile feedback when I push the button, so I assume something tiny is inside making a contact. Maybe I'll try a vacuum cleaner.

Posted at 2021-12-12 by PeterS

I am in the same situation, also after a firmware update through the firmware app. The firmware update did not work, but after reboot , long press button, it came in this loop. DFU with nRF fails with an error. Button is not stuck because when pressing it, I get the loading===== part. Is it possible to load new firmware via serial?

Posted at 2021-12-12 by ajkm

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.

Posted at 2021-12-12 by PeterS

Yes, it worked, thank you, with patience I got to 100% and then rebooted with the new firmware.

Posted at 2021-12-12 by ajkm

Excellent! It really shouldn't be this hard...

Posted at 2021-12-12 by johan_m_o

It normally isn't...

Using the nRF tool to update isn't the most user friendly method, but the issues you experienced isn't normal and hopefully the issue should be fixed now that you've managed to update. Once Gordon gets the App loader firmware updater working it'll be a breeze...

Posted at 2021-12-13 by ajkm

Ha, yep! Thanks.

Posted at 2021-12-13 by @gfwilliams

@ajkm @peters what devices were you using nRF toolbox/connect on? And was it nRF toolbox, or nRF connect? It all works fine here so if there's a specific type of phone it doesn't work properly on it'd be good to know!

Posted at 2021-12-13 by ajkm

nRF Toolbox on iPhone 11 Pro Max, iOS 15.1.

The watch disconnected every 1% of the transfer, but clicking on Retry each time seemed to work to get it to advance in % until it finally reached 100%. When it rebooted it showed .244 and everything is now working just fine.

I can't remember, is there an instruction that the first thing to when Bangle arrives is update the FW? That might have been the case, but I don't think the FW Update app was doing what it says on the tin at that point?

Posted at 2021-12-13 by @gfwilliams

Yes, although to be fair the FW update app has only been like that since Friday morning. Before then it was labelled BETA (like it is again now) and points people at the NRF toolbox example.

... maybe the disconnects are an iPhone thing. What device do you have @peters?

Posted at 2021-12-13 by PeterS

nRF toolbox on iPhone SE on 15.1. I used this tool for my bangle.js 1 without issues before. Response and steps to solve as @ajkm has mentioned.

Posted at 2021-12-13 by htky

Honor 20 with Android 10 here, updated to 2v10.244 smoothly 2 days ago.
I guess it's an iPhone issue only.

Edit: I have an old gen iPhone SE laying around. If need be, I can try to flash newest firmware from that

Posted at 2021-12-14 by @gfwilliams

Thanks @HTKY - well, it does sound a lot like an Apple issue. I just tried on an iPad mini with 12.5.5 and it works great though.

It could be that in newer versions of iOS Apple have started automatically disconnecting Bluetooth devices if they're not bonded after a timeout - it'd explain this issue, and it's in line with Apple's general 'we know what's best for you' attitude to users/developers :(

@peters / @ajkm you could try the 'NRF connect' (not toolbox) app instead I guess, just in case it happens to be any more reliable. Otherwise it is possible to do updates using the Web IDE as well.

Posted at 2021-12-14 by ajkm

Thanks, Gordon.

I ended up using nRF Toolbox because I couldn't use the Web IDE - that was downloading the Hex file instead of the zip file, so kept returning the error.

All's good for now though!

Posted at 2021-12-14 by PeterS

Just tried nRF connect, after 0 bytes it stops with error and there is no option to continue like with nRF toolbox.

Posted at 2021-12-14 by user101594

Yep, @johan_m_o is right - it's a stuck button.

Please could you try pressing it gently and rocking the button up/down/left/right sideways? It's the first I've heard of one getting stuck but there were some cases where the button didn't register clicks and that seemed to fix it fine.

I've tried the suggested technique but had no luck. I can now feel that the "keycap" does not seem to be as well attached - sometimes pressing the button results in instant resistance, but others it slips slightly, or is mushy, before resisting. In both cases I can still register an audible click at the bottom of the travel.

Is there anything else worth doing? Otherwise it's pretty disappointing to have only had a few weeks out of it.

Posted at 2021-12-15 by @gfwilliams

@user101594 email sent