I recovered it! That's fantastic news. But the clues still don't add up, and have me scratching my head. Here's what I did:
I suspected my phone, so I restarted it. No change.
I changed the passkey to the bluetooth, then restarted the Bangle.js. "-> Bluetooth" message still came up after a full reboot.
I was able to pair from my phone and connect, once I gave it the new passkey.
So either the Bangle was telling me it was connected when it wasn't... or something was able to bypass the passkey? Maybe I'm misunderstanding something. Maybe it needs to be turned fully off to drop bluetooth connections?
Also (again from memory, so details are fuzzy) there are times when I've had to connect from my phone's bluetooth menu, and other times when connecting from Gadgetbridge (Bangle.js edition) is enough. So perhaps my phone's bluetooth stack is also lying to me? I would also believe if there were an instability in the phone's bluetooth stack. It has been stable otherwise in my experience, but I know how complex those things are.
But either way, it works and I can get it back after being stuck in this state. I likely didn't need to factory reset it, either. Not having to lose my sleep or fitness data is a plus!
To round out the other questions asked:
I have not used the Web IDE
Test: Touchscreen makes sense. What does it take for the barometer and battery to turn green? They have sensible values, so I can tell they are working.
Working Memory app: If there is a bug, and I'll try to keep an eye out for it. I like to file good bug reports when I can - when I can't help fix them.
And one last question - a Restore from Backup hung about 2/3 of the way through (after waiting ~10 min after progress stopped I called it quits), both times I tried it. I fell back to reinstalling my favorited apps and that worked fine in just about a minute or two. Storage was 90+% empty when I took the backup. Is there anything I might have done wrong there? I'd happily blame either the noisy 2.4 GHz band or my phone's bluetooth instability, but it picked back up without a problem after aborting the Restore and that makes me think it was communicating well enough.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Great, detailed reply. Thank you for the help!
I recovered it! That's fantastic news. But the clues still don't add up, and have me scratching my head. Here's what I did:
So either the Bangle was telling me it was connected when it wasn't... or something was able to bypass the passkey? Maybe I'm misunderstanding something. Maybe it needs to be turned fully off to drop bluetooth connections?
Also (again from memory, so details are fuzzy) there are times when I've had to connect from my phone's bluetooth menu, and other times when connecting from Gadgetbridge (Bangle.js edition) is enough. So perhaps my phone's bluetooth stack is also lying to me? I would also believe if there were an instability in the phone's bluetooth stack. It has been stable otherwise in my experience, but I know how complex those things are.
But either way, it works and I can get it back after being stuck in this state. I likely didn't need to factory reset it, either. Not having to lose my sleep or fitness data is a plus!
To round out the other questions asked:
And one last question - a Restore from Backup hung about 2/3 of the way through (after waiting ~10 min after progress stopped I called it quits), both times I tried it. I fell back to reinstalling my favorited apps and that worked fine in just about a minute or two. Storage was 90+% empty when I took the backup. Is there anything I might have done wrong there? I'd happily blame either the noisy 2.4 GHz band or my phone's bluetooth instability, but it picked back up without a problem after aborting the Restore and that makes me think it was communicating well enough.
Again - thank you!