Update of new watch consistently fails

[bitreaper]

Hi,

I was wondering if others had run into this issue, and if there's any suggestions on how to fix it.  Need to see if there's something I can do before having to RMA the watch.

Preliminary details:

• I bought the dev kit
  
• The sealed watch does not make it through the first update step (upgrade of infinitime from stock 0.7.1 to 1.0)
  
• The dev watch does make it through the update list.
  

I have attempted:

• Following instructions on the update wiki page
  
• using GadgetBridge to upload initially
  
• uninstalling GadgetBridge while using nRF Connect, to ensure there's no conflict
  
• most attempts used nRF Connect, latest version 4.24
  
• Connecting, bonding, changing LE phy from
  
• Trying from two different phones, a Galaxy 20 Note (first attempts) finally going to Galaxy 8 Note.  Same result.
  

Symptoms of each try:

• Gets through some percentage of the load, random each time.  Sometimes 75%, sometimes 18%.
  
• Connection drops, nRF Connect attempts to restart it
  
• watch bluetooth is offline until I reset it with the 8-second-button-press reboot trick.
  
• until retry, watch isn't in scan list
  

It also just occurred to me that while I had the watch charging I was playing with it attached to GadgetBridge, and noticed that some notifications got through, but then it dropped off being attached.  I wonder if the bluetooth transceiver is at fault and not a software glitch.

Thoughts from the community?

UPDATE:  I was finally able to get the watch to update 100%, and then the following updates to the bootloader and rescue went OK as well.  In the true vein of that phrase "definition of insanity is doing the same thing over again and again expecting different results" I tried again.  I think the only thing I changed was letting nRF Connect pick the PHY.  It was glacial to update though compared to the dev watch.  Since then, It hasn't lost bluetooth connectivity to my phone running GadgetBridge.  I'm mostly interested in WASP-OS, so I'll be attempting that later today.  We'll see how that goes.