user159420

Most recent activity

• BangleJS 2 unable to update firmware

  in Bangle.js • 3 days, 3 hours

  

  Thanks for the thorough explanation! I am going to test drive it this week and if I'm having any issue with it I'll reach out to Gordon when he's back in office. I don't mind a mildly shorter-than-advertised battery life; my old watch was only four days or so, so if it's that or better I think I'm good. It was purchased from adafruit if that makes any difference, not sure if going through a particular seller tends to have more issues than another or something.

• BangleJS 2 unable to update firmware

  in Bangle.js • 3 days, 14 hours

  

  YOOOOO!!! That fixed it, thank you so much!

  Does this mean that a normal version will always not work? And is the watch going to behave normally going forward using this version, or do you think it will still need to be replaced? Or did getting it to work normal once mean it will keep acting normal assuming something else doesn't happen?

  Again thank you for the help & your patience with all my questions, this is my first foray into this kind of thing :)

• BangleJS 2 unable to update firmware

  in Bangle.js • 4 days, 2 hours

  

  https://youtu.be/dU1rHN0l004?si=Xtk1HIlc4O2XgHfS
  

  Took a video of it doing everything I can get it to do right now. I have never gotten the WATCHDOG screen, it always says LOCKUP or SW RESET (only on the first time after being turned on). You should be able to hear the button being pressed/released in the video for when I'm holding it.

  I am going to try some of the older firmwares and the alternate storage option later today, I will let you know how it goes.

  And thank you so much for taking the time to help us with this! I'm very excited to get it working (even if it does need to be returned/replaced). Happy new year!

• BangleJS 2 unable to update firmware

  in Bangle.js • 4 days, 12 hours

  

  I tried to do the nrfconnect again a few times today (both with standard version 25 and the cutting edge one) but it didn't work, no longer says bank0 but is back to looping the boot screen. I've been trying to get to the recovery menu since I got the thing but I guess I'm not getting the timing right for when to let go of the button :( it just goes back to looping or shuts off depending on how long I hold it.

  Here's what I can get it to do at this time:
  No action - boot loops
  Hold down button indefinitely - progress bar screen, BOOTING appears at the bottom, screen shuts off momentarily, repeat (I've held it down stupid long, until my finger hurts, and nothing else happens)
  Letting go when BOOTING appears - goes back to boot looping
  Letting go when screen shuts off - stays off
  And of course letting go during the progress bar takes me to the DFU screen.

  Husband just tried to put on the new firmware again via nrfconnect, no change in watch behavior, but sent me the logs which I've attached below.

• BangleJS 2 unable to update firmware

  in Bangle.js • 5 days, 4 hours

  

  Hi guys! I'm the owner of the watch, OP is my husband who beat me to the punch posting here.

  I received it yesterday. Took it out of the box, turned it on, and immediately it kept repeating the booting screen:
  LOCKUP
  BL 2V24
  CHECK STORAGE
  NO NEW FW
  BOOTING

  And then repeating that screen - loading in each line of text, flickering, repeat. I downloaded the nRF updater and tried to install the 2v25 firmware and the app suggested that it had worked (no errors, said completed etc) but nothing changed on the watch. We tried this several times, from both my phone (pixel 7a running grapheneos) and my husband's (stock pixel 9 pro), with the same result. Tried using the app loader website but neither my phone nor my husband's could find the watch using the browser Bluetooth connection.

  Later tried using my husband's laptop which has Bluetooth using the Web IDE and I think the watch died during the attempt since it had been doing the screen repeat the whole drive home (first tries were at the Christmas gathering where I'd received the watch) but we didn't realize at first since we assumed it would power cycle during a firmware update. Once we figured that out and got it charged back up it's been on the BANK0 INVALID since then.

  It never got to the initial splash screen. I took it out of the box, turned it on, and it kept repeating the LOCKUP etc screen before we did anything with it.

  Husband is at work now but I'll be able to respond during the day. Any additional details that would help? Should I try using the nRF updater again? Don't mind having to do any resets or anything since I never got far enough to do any customizing.